Triple
T2392178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Panecillo |
E48967
|
entity |
| Predicate | relativeHeightAboveCity |
P38170
|
FINISHED |
| Object | about 200 meters |
—
|
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 200 meters | Statement: [El Panecillo, relativeHeightAboveCity, about 200 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeHeightAboveCity Context triple: [El Panecillo, relativeHeightAboveCity, about 200 meters]
-
A.
buildingHeightContext
Indicates the contextual or situational factors under which a building’s height is defined, measured, or interpreted.
-
B.
rankInCityByHeight
Indicates the relative ordering of entities within a specific city based on their height, such as which is tallest, second tallest, and so on.
-
C.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
D.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
E.
elevationAboveLake
Indicates the vertical height or altitude of something relative to the surface level of a specified lake.
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc87587708190a7f2bc473a898bc2 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc682d094819081a96ffb77c4c42a |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:57 p.m.