Triple
T36115790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sébastien Ogier |
E1044610
|
entity |
| Predicate | hasFormerCoDriver |
P197214
|
FINISHED |
| Object | Julien Ingrassia |
—
|
NE NERFINISHED |
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: Julien Ingrassia | Statement: [Sébastien Ogier, hasFormerCoDriver, Julien Ingrassia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerCoDriver Context triple: [Sébastien Ogier, hasFormerCoDriver, Julien Ingrassia]
-
A.
hasFormerDriver
Indicates that an entity previously served as a driver for another entity but no longer holds that role.
-
B.
alsoAssociatedWithDriver
Indicates that an entity has an additional or secondary association with a specified driver, beyond any primary or previously stated driver relationship.
-
C.
notableFormerDriver
Indicates that a person was previously a prominent or distinguished driver for the referenced entity (such as a team, organization, or company).
-
D.
runnersUpCoDriver
Indicates that the co-driver finished in a runners-up (non-winning but top) position in a competition or event.
-
E.
hasFormerParticipant
Indicates that an entity once participated in an activity, event, or organization but is no longer a current participant.
- F. None of above. chosen
Provenance (4 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
| PDg | Predicate description generation | batch_69fe7bfb71b08190bed5c33e4ab7afff |
completed | May 9, 2026, 12:12 a.m. |
Created at: May 3, 2026, 4:08 p.m.