Triple
T9950772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peru–Chile border |
E195322
|
entity |
| Predicate | hasHighestElevationInMeters |
P19320
|
FINISHED |
| Object | over 4000 |
—
|
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: over 4000 | Statement: [Peru–Chile border, hasHighestElevationInMeters, over 4000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestElevationInMeters Context triple: [Peru–Chile border, hasHighestElevationInMeters, over 4000]
-
A.
hasHighestPointAboveSeaLevel
Indicates that the highest point of one entity is located at a greater elevation above sea level than that of another entity.
-
B.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
C.
highestElevationApprox
chosen
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
D.
elevationRangeUpperBound
Indicates the maximum elevation value that bounds the upper limit of an elevation range for something.
-
E.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
- 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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb65b83ac8190af6bd8c918ffb69f |
completed | April 2, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:45 p.m.