Triple
T11624041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telescope Peak |
E276213
|
entity |
| Predicate | distanceToBadwaterBasin |
P100639
|
FINISHED |
| Object | approximately 17 mi |
—
|
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: approximately 17 mi | Statement: [Telescope Peak, distanceToBadwaterBasin, approximately 17 mi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBadwaterBasin Context triple: [Telescope Peak, distanceToBadwaterBasin, approximately 17 mi]
-
A.
distanceToDeathValleyJunction
Indicates the measured distance between a given entity’s location and Death Valley Junction.
-
B.
distanceFromBarstow
Indicates the spatial distance between a given location and the reference point of Barstow.
-
C.
distanceToBakersfield
Indicates the spatial distance between a given location and the city of Bakersfield.
-
D.
distanceToFurnaceCreek
Indicates the measured or calculated spatial distance between a given entity and Furnace Creek.
-
E.
distanceFromBrowseBasin_km
Indicates the distance, measured in kilometers, between an entity and the Browse Basin.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a122a3708190ab6513dad4c4fde7 |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.