Triple
T878372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cerro San Cristóbal |
E18972
|
entity |
| Predicate | relativeHeight |
P18367
|
FINISHED |
| Object | about 300 meters above Santiago city level |
—
|
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: about 300 meters above Santiago city level | Statement: [Cerro San Cristóbal, relativeHeight, about 300 meters above Santiago city level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeHeight Context triple: [Cerro San Cristóbal, relativeHeight, about 300 meters above Santiago city level]
-
A.
originalHeight
Indicates the initial or starting height of an entity before any change, adjustment, or transformation occurs.
-
B.
heightReference
chosen
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
C.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
D.
currentHeight
Indicates the present vertical measurement or elevation of an entity at a given point in time.
-
E.
hasRelativeSize
Indicates that one entity’s size is being compared to another entity’s size, expressing a relative rather than absolute magnitude.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acb1dc20819095b9bb093158b60d |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8d47c081909b02a53e305ccf7a |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.