Triple
T33951387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | women's 100 metres hurdles |
E870449
|
entity |
| Predicate | distanceFromLastHurdleToFinish |
P3387
|
FINISHED |
| Object | 10.5 metres |
—
|
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: 10.5 metres | Statement: [women's 100 metres hurdles, distanceFromLastHurdleToFinish, 10.5 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromLastHurdleToFinish Context triple: [women's 100 metres hurdles, distanceFromLastHurdleToFinish, 10.5 metres]
-
A.
winningDistance
Indicates the margin or amount by which a competitor or participant wins over others in a contest or event.
-
B.
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.
-
C.
distancePerRace
Indicates the total distance covered in a single race event or instance.
-
D.
distanceFromTerminus
chosen
Indicates the measured distance of an entity from a defined endpoint or terminus along a route, path, or sequence.
-
E.
finishedSecondInRace
Indicates that an entity completed a race in second place relative to other competitors.
- 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_69f3499c2d7481909c953a5010227725 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:49 a.m.