Triple
T29255396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockport Line |
E741689
|
entity |
| Predicate | connectsToLineAtNorthStation |
P194745
|
FINISHED |
| Object | Fitchburg 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: Fitchburg Line | Statement: [Rockport Line, connectsToLineAtNorthStation, Fitchburg Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToLineAtNorthStation Context triple: [Rockport Line, connectsToLineAtNorthStation, Fitchburg Line]
-
A.
adjacentStationOnNorthernLine
Indicates that one station is directly next to another station along the Northern Line, with no other stations in between.
-
B.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
C.
connectsNorthTo
Indicates that one entity serves as a connection or link from another entity to something located to its north.
-
D.
previousStationOnLine1Northbound
Indicates that one station is immediately before another station when traveling northbound on line 1.
-
E.
hasNeighbouringStationOnNorthLondonLine
Indicates that one station is directly adjacent to another station along the North London Line.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
| PDg | Predicate description generation | batch_69fd8640e1d4819081c98f15eeb221ab |
completed | May 8, 2026, 6:44 a.m. |
Created at: April 28, 2026, 12:37 p.m.