Triple
T34803848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yas Marina 12 Hours |
E1003293
|
entity |
| Predicate | approximateRaceLength |
P199380
|
FINISHED |
| Object | 12 hours of continuous competition |
—
|
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: 12 hours of continuous competition | Statement: [Yas Marina 12 Hours, approximateRaceLength, 12 hours of continuous competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateRaceLength Context triple: [Yas Marina 12 Hours, approximateRaceLength, 12 hours of continuous competition]
-
A.
raceDistanceApprox
Indicates that the distance of a race is approximately equal to a specified value, allowing for some margin of error rather than requiring an exact match.
-
B.
approximateLengthInMeters
Indicates the estimated or roughly measured length of something expressed in meters.
-
C.
distancePerRace
Indicates the total distance covered in a single race event or instance.
-
D.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
-
E.
typicalRaceLengthCategory
Indicates the usual distance range or length classification that a race is most commonly run at.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
| PDg | Predicate description generation | batch_69ff32b6dd448190a7a6ebb76b99d4cc |
completed | May 9, 2026, 1:12 p.m. |
Created at: May 3, 2026, 3:59 p.m.