Triple
T26147857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona State Route 24 |
E659728
|
entity |
| Predicate | futureExtensionDirection |
P19358
|
FINISHED |
| Object | eastward |
—
|
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: eastward | Statement: [Arizona State Route 24, futureExtensionDirection, eastward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureExtensionDirection Context triple: [Arizona State Route 24, futureExtensionDirection, eastward]
-
A.
plannedExtensionDirection
chosen
Indicates the intended directional path or orientation along which something is planned to be extended in the future.
-
B.
extendedTowards
Indicates that one entity is stretched or directed outward in the direction of another entity or location.
-
C.
futureComponentOf
Indicates that one entity is expected or planned to become a component or part of another entity at some point in the future.
-
D.
plannedExtensionTo
Indicates that one entity is intended or scheduled to be extended, expanded, or continued by another entity in the future.
-
E.
futurePosition
Indicates that one entity will occupy or hold the position, role, or location of another entity at a later point in time.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60be993dc819083bd352e2b444611 |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:23 p.m.