Triple
T9754186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flo |
E236512
|
entity |
| Predicate | hasPartInPlot |
P17462
|
FINISHED |
| Object | helps welcome Lightning McQueen to Radiator Springs |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: helps welcome Lightning McQueen to Radiator Springs | Statement: [Flo, hasPartInPlot, helps welcome Lightning McQueen to Radiator Springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartInPlot Context triple: [Flo, hasPartInPlot, helps welcome Lightning McQueen to Radiator Springs]
-
A.
plotInvolvement
chosen
Indicates that an entity participates in, contributes to, or is affected by the events or storyline of a narrative work.
-
B.
hasPartInNarrative
Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
-
C.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
-
D.
hasPartIn
Indicates that an entity participates in or plays a role within a larger event, process, or composite entity.
-
E.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca84d4eddc8190996fec1417d2bae8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9fb01ad08190b2435fa505c622bc |
completed | April 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69cd03d0772c8190bd1750cf1cfba309 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:24 p.m.