Triple
T15723104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Diente Peak |
E381150
|
entity |
| Predicate | hasCountyHighPointRelation |
P112251
|
FINISHED |
| Object | one of the highest peaks in Montezuma County |
—
|
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: one of the highest peaks in Montezuma County | Statement: [El Diente Peak, hasCountyHighPointRelation, one of the highest peaks in Montezuma County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountyHighPointRelation Context triple: [El Diente Peak, hasCountyHighPointRelation, one of the highest peaks in Montezuma County]
-
A.
highPointLocatedOn
Indicates that the highest point of one entity is situated on or atop another entity.
-
B.
containsHighestPointOf
chosen
Indicates that one entity includes within its boundaries the location of the highest point of another entity.
-
C.
hasHighestPointType
Indicates that the highest point of an entity is of a specified type or category.
-
D.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
E.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb1fdd4819088f3e243263e5f73 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.