Triple
T27454284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona State Route 69 |
E692540
|
entity |
| Predicate | terminusConnectsTo |
P167776
|
FINISHED |
| Object | Interstate 17 near Cordes Junction |
—
|
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: Interstate 17 near Cordes Junction | Statement: [Arizona State Route 69, terminusConnectsTo, Interstate 17 near Cordes Junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusConnectsTo Context triple: [Arizona State Route 69, terminusConnectsTo, Interstate 17 near Cordes Junction]
-
A.
terminusWestConnection
Indicates that one entity serves as the western endpoint where it connects to another entity or route.
-
B.
terminusSouthConnection
Indicates a connection where one entity serves as the southern terminus or endpoint of another entity.
-
C.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
D.
terminusAdjacentTo
Indicates that one terminus (end point) of a route, line, or feature is directly next to or immediately bordering another terminus.
-
E.
terminusTowards
Indicates that one entity serves as the endpoint or directional terminus oriented toward another entity.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 27, 2026, 12:48 p.m.