Triple
T22196704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maipo Andes |
E548567
|
entity |
| Predicate | altitudeRelativeToMaipoValley |
P146802
|
FINISHED |
| Object | higher-altitude |
—
|
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: higher-altitude | Statement: [Maipo Andes, altitudeRelativeToMaipoValley, higher-altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: altitudeRelativeToMaipoValley Context triple: [Maipo Andes, altitudeRelativeToMaipoValley, higher-altitude]
-
A.
elevationRelativeToTehachapiMountains
Indicates the relative elevation of an entity compared to the elevation of the Tehachapi Mountains.
-
B.
elevationRelativeToCanyon
Indicates the relative height or altitude of one location compared to the canyon’s reference level.
-
C.
valleyHeightAboveGround
Indicates the vertical distance between the valley’s lowest point and the surrounding ground level.
-
D.
elevationRelativeToCanyonFloor
Indicates the vertical height or altitude of something measured relative to the canyon floor as the reference level.
-
E.
distanceToAlturas
Indicates the measured distance between a given entity’s location and the location of Alturas.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12ae7c72081909b7817d66391bef4 |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:35 p.m.