Triple
T29255383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockport Line |
E741689
|
entity |
| Predicate | primaryStationInBoston |
P99762
|
FINISHED |
| Object | North Station |
—
|
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: North Station | Statement: [Rockport Line, primaryStationInBoston, North Station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStationInBoston Context triple: [Rockport Line, primaryStationInBoston, North Station]
-
A.
primaryStation
Indicates that one station is designated as the main or principal station associated with another entity or within a given context.
-
B.
mainLocationWithinBoston
chosen
Indicates that the primary or central location of an entity is situated within the geographic boundaries of Boston.
-
C.
isOneOfMajorStationsIn
Indicates that a station belongs to the set of primary or most important stations within a specified area or system.
-
D.
precedingStationOnRedLineTowardAlewife
Indicates that one station is immediately before another station on the Red Line in the direction of travel toward Alewife.
-
E.
formerMainlineStation
Indicates that a station previously served as a mainline station but no longer holds that status.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a00d15f7b788190a3bf440be7837192 |
completed | May 10, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_6a00d0f8ef548190b1c15b06164eec4a |
completed | May 10, 2026, 6:39 p.m. |
Created at: April 28, 2026, 12:37 p.m.