Triple
T34881406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruta Nacional 51 |
E1006019
|
entity |
| Predicate | hasHighAltitudeSections |
P180937
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ruta Nacional 51, hasHighAltitudeSections, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighAltitudeSections Context triple: [Ruta Nacional 51, hasHighAltitudeSections, true]
-
A.
isHighElevation
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
-
B.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
C.
hasMountainSections
chosen
Indicates that a route, area, or path includes one or more segments that pass through or are characterized by mountainous terrain.
-
D.
hasAltitudeDifference
Indicates that there is a specific vertical height difference between two entities or locations.
-
E.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
- 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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff2d22ffb48190ae58ddf3c7e02869 |
completed | May 9, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69ff2ac2e1c4819096cc64e94aef2ff0 |
completed | May 9, 2026, 12:38 p.m. |
Created at: May 3, 2026, 4 p.m.