Triple
T26728819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cordillera Central (Colombian Andes) |
E673908
|
entity |
| Predicate | positionInColombianAndes |
P132440
|
FINISHED |
| Object | central branch |
—
|
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: central branch | Statement: [Cordillera Central (Colombian Andes), positionInColombianAndes, central branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInColombianAndes Context triple: [Cordillera Central (Colombian Andes), positionInColombianAndes, central branch]
-
A.
positionInColombia
Indicates that one entity occupies or is located at a specific position within the geographic boundaries of Colombia.
-
B.
isInCountryWithAndes
Indicates that an entity is located in a country whose territory includes part of the Andes mountain range.
-
C.
partOfAndeanRegion
chosen
Indicates that something is geographically or administratively included within the Andean region.
-
D.
isTransAndean
Indicates that something is located across, beyond, or on the opposite side of the Andes Mountains relative to a given reference point.
-
E.
elevationRelativeToQuito
Indicates the relative elevation difference between a location and the city of Quito.
- 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_69eecda481d08190aea69f2f7c745f56 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 3:44 a.m.