Triple
T10543498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexico City Metro Line 6 |
E248754
|
entity |
| Predicate | routeLengthKilometres |
P68820
|
FINISHED |
| Object | 13.947 |
—
|
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: 13.947 | Statement: [Mexico City Metro Line 6, routeLengthKilometres, 13.947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeLengthKilometres Context triple: [Mexico City Metro Line 6, routeLengthKilometres, 13.947]
-
A.
lengthInKm
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
-
B.
trackLengthApproxKm
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
-
C.
range_km
Indicates the maximum distance, measured in kilometers, over which something can operate, travel, or be effective.
-
D.
tourLength
Indicates the total duration or distance covered by a tour or route.
-
E.
totalRouteLength
chosen
Indicates the overall distance or length of an entire route when all its segments are combined.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d51911b10481909e6e548879e8de36 |
completed | April 7, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69d4fb9729288190a0149f127acd7ae3 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:32 p.m.