Triple
T13843366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Pecho |
E332725
|
entity |
| Predicate | relativePositionOnMountain |
P44470
|
FINISHED |
| Object | central summit of Iztaccíhuatl |
—
|
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: central summit of Iztaccíhuatl | Statement: [El Pecho, relativePositionOnMountain, central summit of Iztaccíhuatl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativePositionOnMountain Context triple: [El Pecho, relativePositionOnMountain, central summit of Iztaccíhuatl]
-
A.
positionRelativeToSummit
chosen
Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
-
B.
endPointMountain
Indicates that a path, route, or boundary terminates at a mountain.
-
C.
sideOfMountain
Indicates that one entity is located on or corresponds to a particular side or face of a mountain relative to another entity.
-
D.
relativeToMountEverest
Indicates a relationship that compares or situates something in reference to Mount Everest, such as in terms of location, height, scale, or significance.
-
E.
distanceToSummit
Indicates the measured or estimated distance remaining from a given point to the summit of a feature or elevation.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02afce788190a74dce4e6a3569fa |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.