Triple
T28069154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parker Road Station |
E709342
|
entity |
| Predicate | hasThroughRouting |
P26302
|
FINISHED |
| Object | Red Line |
—
|
NE NERFINISHED |
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: Red Line | Statement: [Parker Road Station, hasThroughRouting, Red Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThroughRouting Context triple: [Parker Road Station, hasThroughRouting, Red Line]
-
A.
hasThroughServiceWith
chosen
Indicates that two transportation services are operationally linked so that a passenger or shipment can continue from one to the other without a separate booking or major interruption.
-
B.
hasRouteConsideration
Indicates that one entity takes another entity into account when planning, evaluating, or determining a route.
-
C.
supportsRouting
Indicates that one entity provides the capability to determine and direct paths or routes for another entity’s traffic, requests, or messages.
-
D.
hasAlongRoute
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
E.
supportsHierarchicalRouting
Indicates that one entity enables or is compatible with routing that uses a multi-level or hierarchical structure of routing domains or paths.
- 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 8:45 p.m.