Triple
T32255949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seligman, Arizona |
E824022
|
entity |
| Predicate | transportShift |
P197526
|
FINISHED |
| Object | bypassed by Interstate 40 |
—
|
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: bypassed by Interstate 40 | Statement: [Seligman, Arizona, transportShift, bypassed by Interstate 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportShift Context triple: [Seligman, Arizona, transportShift, bypassed by Interstate 40]
-
A.
transportActivity
Indicates an activity in which something or someone is moved or carried from one place to another.
-
B.
transportModeTo
Indicates the means or mode of transportation used to travel to a specified destination.
-
C.
transportDevelopment
Indicates the development or improvement of transportation systems, infrastructure, or services connecting places or entities.
-
D.
transportSubmode
Indicates a more specific categorization of a general transport mode, defining the particular sub-type or variant of transportation being used.
-
E.
transportProject
Indicates a project whose primary purpose is to plan, build, improve, or manage transportation systems, services, or infrastructure.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69fe991abc6c81908edbb98d61c9ca73 |
completed | May 9, 2026, 2:16 a.m. |
Created at: May 1, 2026, 12:41 a.m.