Triple
T19151998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | men's individual sprint at the 2008 Summer Olympics |
E468830
|
entity |
| Predicate | lapLengthOfTrack |
P134623
|
FINISHED |
| Object | 250 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: 250 metres | Statement: [men's individual sprint at the 2008 Summer Olympics, lapLengthOfTrack, 250 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lapLengthOfTrack Context triple: [men's individual sprint at the 2008 Summer Olympics, lapLengthOfTrack, 250 metres]
-
A.
laneLength
Indicates the length or distance of a lane in a given context.
-
B.
longestTrack
Indicates that the related track is the one with the greatest duration or length among a given set of tracks.
-
C.
typicalTrackLengthRange
Indicates the usual minimum and maximum lengths that a track associated with something tends to fall between.
-
D.
trackLengthApproxKm
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
-
E.
mainTrackDistance
Indicates the distance measured along the primary or main track between two referenced points or entities.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e97dc5a481909a58416126a0862d |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:06 p.m.