Triple
T27010931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ritacuba Blanco |
E680380
|
entity |
| Predicate | mainNormalRouteFrom |
P134444
|
FINISHED |
| Object | El Cocuy |
—
|
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: El Cocuy | Statement: [Ritacuba Blanco, mainNormalRouteFrom, El Cocuy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainNormalRouteFrom Context triple: [Ritacuba Blanco, mainNormalRouteFrom, El Cocuy]
-
A.
onStandardRouteOf
Indicates that something lies along or follows the usual, predefined, or officially designated route of another entity.
-
B.
primaryRouteFrom
chosen
Indicates that one entity serves as the main or preferred route originating from another entity.
-
C.
majorRouteTo
Indicates that one location serves as a primary or significant route or pathway leading to another location.
-
D.
originalRoute
Indicates that one route is the initial or primary path from which another route is derived, modified, or compared.
-
E.
standardRouteStartsFrom
Indicates that a standard or predefined route has its starting point at a specified location or entity.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621d6eeb8819091c42b69b26b4d8a |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7:03 a.m.