Triple
T29815334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCI velodrome standards |
E757087
|
entity |
| Predicate | standardOlympicTrackLength |
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: [UCI velodrome standards, standardOlympicTrackLength, 250 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardOlympicTrackLength Context triple: [UCI velodrome standards, standardOlympicTrackLength, 250 metres]
-
A.
perimeterRunningTrackLength
Indicates the length of a running track that follows the perimeter of a given area or facility.
-
B.
lapLengthOfTrack
chosen
Indicates the distance or length of a single lap around a track.
-
C.
standardMileLength
Indicates that there is a specified conventional or officially accepted length associated with a mile.
-
D.
isLongTrack
Indicates that something (such as a route, path, or recording) has a relatively great length or duration compared to typical or standard examples of its kind.
-
E.
typicalRaceDistanceUnit
Indicates the standard unit of measurement used to express the usual race distance associated with an entity.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 29, 2026, 5:26 p.m.