Triple
T30771572
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trona, California |
E783536
|
entity |
| Predicate | distanceToDeathValleyNationalPark |
P133072
|
FINISHED |
| Object | about 60 miles |
—
|
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: about 60 miles | Statement: [Trona, California, distanceToDeathValleyNationalPark, about 60 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDeathValleyNationalPark Context triple: [Trona, California, distanceToDeathValleyNationalPark, about 60 miles]
-
A.
distanceToDeathValleyNationalParkEntrance
chosen
Indicates the measured distance between a given entity’s location and the entrance of Death Valley National Park.
-
B.
distanceToDeathValleyJunction
Indicates the measured distance between a given entity’s location and Death Valley Junction.
-
C.
distanceToBadwaterBasin
Indicates the measured spatial distance between a given entity and Badwater Basin.
-
D.
distanceToWitney
Indicates the spatial distance between an entity and the location Witney.
-
E.
distanceToYosemiteNationalPark
Indicates the measured distance between a given entity’s location and Yosemite National Park.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01487b73488190954eb5143e6f246e |
completed | May 11, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_6a0145210ae481908da59b02efdbc397 |
completed | May 11, 2026, 2:55 a.m. |
Created at: April 29, 2026, 8:40 p.m.