Triple
T31250969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Cauca |
E796815
|
entity |
| Predicate | traversedByMountainRange |
P651
|
FINISHED |
| Object | Andes |
—
|
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: Andes | Statement: [Department of Cauca, traversedByMountainRange, Andes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traversedByMountainRange Context triple: [Department of Cauca, traversedByMountainRange, Andes]
-
A.
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.
-
B.
crossesMountainRange
Indicates that one entity traverses from one side of a mountain range to the other, passing through or over it.
-
C.
hasMountainRange
chosen
Indicates that one entity possesses, contains, or is geographically associated with a specific mountain range.
-
D.
crossesMountainPass
Indicates that an entity traverses from one side of a mountain range to another via a defined mountain pass.
-
E.
mountainRangeClimbedIn
Indicates that a particular mountain range is the location in which a climbing activity or ascent took place.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 29, 2026, 9:11 p.m.