Triple
T19658020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA Lowell Line |
E471999
|
entity |
| Predicate | connectsToBusAt |
P136848
|
FINISHED |
| Object | multiple intermediate stations |
—
|
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: multiple intermediate stations | Statement: [MBTA Lowell Line, connectsToBusAt, multiple intermediate stations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToBusAt Context triple: [MBTA Lowell Line, connectsToBusAt, multiple intermediate stations]
-
A.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
B.
busConnectorLocation
Indicates the physical position or placement of a bus connector relative to the system or components it connects.
-
C.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
D.
hasBusInterchange
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
E.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641475f408190bd42ef3f8d590719 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:45 p.m.