Triple
T31222433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wenden, Arizona |
E796047
|
entity |
| Predicate | distanceToPhoenixInMiles |
P40233
|
FINISHED |
| Object | approximately 100 |
—
|
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 100 | Statement: [Wenden, Arizona, distanceToPhoenixInMiles, approximately 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToPhoenixInMiles Context triple: [Wenden, Arizona, distanceToPhoenixInMiles, approximately 100]
-
A.
distanceToPhoenix
chosen
Indicates the measured or estimated distance between a given entity’s location and the city of Phoenix.
-
B.
distanceToPrescottInMiles
Indicates the numerical distance, measured in miles, between a given entity and Prescott.
-
C.
distanceFromTucson
Indicates the spatial distance between a given entity and the location of Tucson.
-
D.
distanceToSedona
Indicates the measured or calculated spatial distance between a given entity’s location and the location of Sedona.
-
E.
distanceToFlagstaff
Indicates the measured distance between a given entity’s location and the location of Flagstaff.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01b130f6808190b86442fb16930e6e |
completed | May 11, 2026, 10:36 a.m. |
| PD | Predicate disambiguation | batch_6a01b023157881909a802e06eced3e2f |
completed | May 11, 2026, 10:32 a.m. |
Created at: April 29, 2026, 9:10 p.m.