Triple
T8402684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston, Nevada |
E198412
|
entity |
| Predicate | highestNearbyPeakElevationInFeet |
P81817
|
FINISHED |
| Object | 11577 |
—
|
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: 11577 | Statement: [Kingston, Nevada, highestNearbyPeakElevationInFeet, 11577]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestNearbyPeakElevationInFeet Context triple: [Kingston, Nevada, highestNearbyPeakElevationInFeet, 11577]
-
A.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
B.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
-
C.
nearbyElevation
Indicates that one entity is located at or associated with an elevation that is geographically close to the elevation of another entity.
-
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. 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb824efa5c81908ce816cdb8e1fcfb |
completed | March 31, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:04 p.m.