Triple
T32069509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piston Cup racing |
E818971
|
entity |
| Predicate | notableRacer |
P206171
|
FINISHED |
| Object | Lightning McQueen |
E236507
|
NE 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: Lightning McQueen | Statement: [Piston Cup racing, notableRacer, Lightning McQueen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRacer Context triple: [Piston Cup racing, notableRacer, Lightning McQueen]
-
A.
notableRaceEngineer
Indicates that the person is recognized as a significant or distinguished engineer in the context of racing or motorsport.
-
B.
notableRiderType
Indicates that an entity is notably associated with a particular type or category of rider (e.g., cyclist, jockey, driver).
-
C.
notableRacingVariant
Indicates that one entity is a particularly recognized or distinguished racing-specific version or trim of another entity.
-
D.
racingDriver
Indicates that one entity is a racing driver, i.e., a person who competes in motor races as a driver.
-
E.
notableRiderAssociation
Indicates a significant or well-known connection between a rider and another entity, such as a horse, team, or event.
- F. None of above. chosen
Provenance (5 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34c65a4a7c819091a10230b133c090 |
completed | June 19, 2026, 4:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:23 a.m.