Triple
T31211452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cascada Grande |
E795752
|
entity |
| Predicate | relativeToCascadaChica |
P207373
|
FINISHED |
| Object | larger |
—
|
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: larger | Statement: [Cascada Grande, relativeToCascadaChica, larger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToCascadaChica Context triple: [Cascada Grande, relativeToCascadaChica, larger]
-
A.
relativeLocationWithinPisac
Indicates that one entity is located within the spatial or geographic boundaries of Pisac.
-
B.
hasRelativePositionOnCerroDeLaSilla
Indicates that one entity has a specific spatial or locational relationship relative to Cerro de la Silla.
-
C.
nearbyCanyon
Indicates that one entity is located close to a canyon in spatial proximity.
-
D.
hasRelativePositionToLicancabur
Indicates that one entity has a specific spatial or geographic position defined in relation to Licancabur.
-
E.
elevationRelativeToCanyon
Indicates the relative height or altitude of one location compared to the canyon’s reference level.
- F. None of above. chosen
Provenance (4 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:09 p.m.