Triple
T29815336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UCI velodrome standards |
E757087
|
entity |
| Predicate | standardTrackWidthRange |
P63008
|
FINISHED |
| Object | 7–8 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: 7–8 metres | Statement: [UCI velodrome standards, standardTrackWidthRange, 7–8 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTrackWidthRange Context triple: [UCI velodrome standards, standardTrackWidthRange, 7–8 metres]
-
A.
trackWidth
chosen
Indicates the lateral distance between two parallel tracks or wheels, typically measured from center to center.
-
B.
typicalTrackLengthRange
Indicates the usual minimum and maximum lengths that a track associated with something tends to fall between.
-
C.
typicalTrackCharacteristics
Indicates that the associated characteristics represent the usual or standard features of a given track.
-
D.
hasRailWidth
Indicates that one entity has a specified width measurement for its rail or rails.
-
E.
typicalLugWidth
Indicates the standard or commonly used width of a lug in a given context or application.
- 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_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 5:26 p.m.