Triple
T34147648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argyle station (CTA) |
E875904
|
entity |
| Predicate | directionOfService |
P13415
|
FINISHED |
| Object | northbound |
—
|
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: northbound | Statement: [Argyle station (CTA), directionOfService, northbound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionOfService Context triple: [Argyle station (CTA), directionOfService, northbound]
-
A.
serviceDirection
chosen
Indicates the direction or orientation in which a service is provided or operates relative to involved entities.
-
B.
serviceDirectionDetail
Indicates the specific directional or routing details associated with a service, such as the way or path it operates between points.
-
C.
servedByDirection
Indicates that something (such as a route, service, or facility) is provided or accessed in a specific directional orientation (e.g., northbound, inbound).
-
D.
parallelServiceDirection
Indicates that two services operate in the same or corresponding direction, running parallel to each other in their routing or flow.
-
E.
providesServiceTowards
Indicates that one entity delivers or performs a service directed to or for the benefit of another entity.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 1, 2026, 1:54 a.m.