Triple
T35036925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olivier Pla |
E1010944
|
entity |
| Predicate | hasCompetitorRole |
P33874
|
FINISHED |
| Object | Le Mans Prototype driver |
—
|
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: Le Mans Prototype driver | Statement: [Olivier Pla, hasCompetitorRole, Le Mans Prototype driver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitorRole Context triple: [Olivier Pla, hasCompetitorRole, Le Mans Prototype driver]
-
A.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
B.
hadCompetitorType
Indicates that an entity had a competitor belonging to a specified type or category.
-
C.
competitionRole
chosen
Indicates that an entity holds a specific role, position, or function within a competitive event or contest.
-
D.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
E.
hasEntrantRole
Indicates that an entity participates in an event, competition, or process specifically in the capacity of an entrant or participant.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.