Triple
T2565904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sedona |
E57349
|
entity |
| Predicate | distanceToFlagstaff |
P40232
|
FINISHED |
| Object | approximately 30 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: approximately 30 miles | Statement: [Sedona, distanceToFlagstaff, approximately 30 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToFlagstaff Context triple: [Sedona, distanceToFlagstaff, approximately 30 miles]
-
A.
distanceFromSaltLakeCity
Indicates the measured distance between a given location and Salt Lake City.
-
B.
distanceFromSocorro
Indicates the spatial distance between an entity and the reference location Socorro.
-
C.
distanceToSaltLakeCity
Indicates the measured or calculated distance between a given entity’s location and the city of Salt Lake City.
-
D.
distanceToLosAngeles
Indicates the measured or calculated distance between a given entity’s location and the city of Los Angeles.
-
E.
distanceFromAlamogordo
Indicates the spatial distance between a given entity and the location of Alamogordo.
- 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_69ab4a4ef9008190a0e6d4422b9418b7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd35ef22c8190966612cc75f69eca |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1aa13a08190a8757c017d8a2478 |
completed | March 7, 2026, 7:20 a.m. |
Created at: March 6, 2026, 9:48 p.m.