Triple
T8380903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 × 400 metres relay at the 1924 Summer Olympics |
E197684
|
entity |
| Predicate | legDistanceUnit |
P66191
|
FINISHED |
| Object | 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: metres | Statement: [4 × 400 metres relay at the 1924 Summer Olympics, legDistanceUnit, metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legDistanceUnit Context triple: [4 × 400 metres relay at the 1924 Summer Olympics, legDistanceUnit, metres]
-
A.
dimensionOfLength
Indicates that something represents or specifies a measurement along a single spatial extent (a length dimension).
-
B.
typicalRaceDistanceUnit
chosen
Indicates the standard unit of measurement used to express the usual race distance associated with an entity.
-
C.
runwayLengthUnit
Indicates the unit of measurement used to express the length of a runway in the relationship.
-
D.
dimensions_km
Indicates the physical size or extent of something measured in kilometers, typically specifying one or more linear dimensions (e.g., length, width, height).
-
E.
raceDistanceType
Indicates the specific type or category of distance over which a race is conducted.
- 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_69ca82f64c188190af4e1608036b865d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80c57080819097eef2b7e46eaaee |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:02 p.m.