Triple
T23280986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treasure Mountain (Colorado) |
E588860
|
entity |
| Predicate | nearestMajorMountainRangeCenter |
P100660
|
FINISHED |
| Object | near the core of the Elk Mountains |
—
|
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: near the core of the Elk Mountains | Statement: [Treasure Mountain (Colorado), nearestMajorMountainRangeCenter, near the core of the Elk Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMajorMountainRangeCenter Context triple: [Treasure Mountain (Colorado), nearestMajorMountainRangeCenter, near the core of the Elk Mountains]
-
A.
nearbyMountainRegion
chosen
Indicates that one location is situated close to or within the surrounding area of a mountainous region.
-
B.
nearbySummit
Indicates that one summit is located close to another summit in geographic space.
-
C.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to another entity.
-
D.
hasHighestPointNear
Indicates that one entity’s highest point is located close to another specified entity or location.
-
E.
endPointMountain
Indicates that a path, route, or boundary terminates at a mountain.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19642b46481909fd455acd2155792 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:56 p.m.