Triple
T161744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boston’s North Station (via Fitchburg Line) |
E3301
|
entity |
| Predicate | railNetworkSide |
P6244
|
FINISHED |
| Object | northside |
—
|
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: northside | Statement: [Boston’s North Station (via Fitchburg Line), railNetworkSide, northside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railNetworkSide Context triple: [Boston’s North Station (via Fitchburg Line), railNetworkSide, northside]
-
A.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
-
B.
hasRailSystem
Indicates that an entity possesses or is served by a rail-based transportation system.
-
C.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
D.
railwayDivision
Indicates that one administrative railway division is responsible for, manages, or encompasses another railway unit, line, or area within a rail network.
-
E.
drivingSide
Indicates which side of the road (left or right) vehicles are required to drive on in a given jurisdiction.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2585877648190a2ec320182a69343 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256623704819089d9eeefe05858ce |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2578329d08190be82e004b8224d2b |
completed | Feb. 28, 2026, 2:48 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.