Triple
T8630615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIA World Endurance Championship |
E204389
|
entity |
| Predicate | longestRaceDuration |
P40964
|
FINISHED |
| Object | 24 hours |
—
|
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: 24 hours | Statement: [FIA World Endurance Championship, longestRaceDuration, 24 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longestRaceDuration Context triple: [FIA World Endurance Championship, longestRaceDuration, 24 hours]
-
A.
longestDurationAt
chosen
Indicates that one entity has the greatest length of time associated with a particular state, event, or activity compared to other relevant entities.
-
B.
majorRaceDistance
Indicates the standard or primary distance over which a major race or competition is contested.
-
C.
timingOfRace
Indicates the temporal details or schedule associated with a race, such as its start time, duration, or overall timing.
-
D.
mostRuns
Indicates that one entity has scored a greater number of runs than all comparable entities in a given context or set.
-
E.
raceRecord
Indicates that there exists a recorded result or performance entry for an entity participating in a race or competitive event.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.