Triple
T25796671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heber City |
E649703
|
entity |
| Predicate | distanceToProvo |
P190472
|
FINISHED |
| Object | approximately 30 miles northeast |
—
|
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 30 miles northeast | Statement: [Heber City, distanceToProvo, approximately 30 miles northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToProvo Context triple: [Heber City, distanceToProvo, approximately 30 miles northeast]
-
A.
distanceToOgden
Indicates the spatial distance between an entity and the location named Ogden.
-
B.
distanceFromSaltLakeCity
Indicates the measured distance between a given location and Salt Lake City.
-
C.
distanceToSaltLakeCity
Indicates the measured or calculated distance between a given entity’s location and the city of Salt Lake City.
-
D.
distanceToProvidence
Indicates the measured spatial distance between a given entity’s location and the location of Providence.
-
E.
distanceFromLasVegas
Indicates the measured distance between a given place or object and the city of Las Vegas.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: April 22, 2026, 6:31 a.m.