Triple
T32621931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pisiga–Colchane |
E833948
|
entity |
| Predicate | crossesHighAltitudePlateau |
P73807
|
FINISHED |
| Object | Altiplano |
—
|
NE NERFINISHED |
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: Altiplano | Statement: [Pisiga–Colchane, crossesHighAltitudePlateau, Altiplano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesHighAltitudePlateau Context triple: [Pisiga–Colchane, crossesHighAltitudePlateau, Altiplano]
-
A.
crossesMountainPass
Indicates that an entity traverses from one side of a mountain range to another via a defined mountain pass.
-
B.
crossesMountainRange
Indicates that one entity traverses from one side of a mountain range to the other, passing through or over it.
-
C.
crossesMountainRangeTo
Indicates that one entity traverses from one side of a mountain range to the other, passing across or through it as a route or connection.
-
D.
isHighElevation
chosen
Indicates that an entity is located at or associated with a relatively high altitude or elevation above a reference level, typically sea level.
-
E.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
- 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_69f3492ccc80819086ef7d26e9786647 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:06 a.m.