Triple
T1147948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PHX Sky Train |
E23609
|
entity |
| Predicate | phaseOneRoute |
P21548
|
FINISHED |
| Object | 44th Street/Washington station to Terminal 4 |
—
|
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: 44th Street/Washington station to Terminal 4 | Statement: [PHX Sky Train, phaseOneRoute, 44th Street/Washington station to Terminal 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: phaseOneRoute Context triple: [PHX Sky Train, phaseOneRoute, 44th Street/Washington station to Terminal 4]
-
A.
parallelRoute
Indicates that one route runs alongside and in the same general direction as another route without intersecting it.
-
B.
firstRoutes
chosen
Indicates that one route or path is the initial or primary route taken or assigned among a set of possible routes.
-
C.
primaryRoute
Indicates that one route is designated as the main or preferred path among possible alternatives between locations.
-
D.
nextRoute
Indicates that one route directly follows another in a defined sequence or ordering of routes.
-
E.
mainPhase
Indicates that an event, action, or state occurs during the primary or central phase of a larger process or sequence.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.