Triple
T37728531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mattapan trolley line |
E940089
|
entity |
| Predicate | terminusHasStation |
P34947
|
FINISHED |
| Object | Capen Street 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: Capen Street station | Statement: [Mattapan trolley line, terminusHasStation, Capen Street station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusHasStation Context triple: [Mattapan trolley line, terminusHasStation, Capen Street station]
-
A.
terminusStation
Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
-
B.
terminusConnectsTo
Indicates that a transportation route’s endpoint is directly linked or transitions to another route, line, or terminal.
-
C.
hasEndpointStation
chosen
Indicates that something (such as a route, line, or service) has a specific station as one of its terminal endpoints.
-
D.
railLineTerminus
Indicates that a rail line ends or terminates at the specified location or station.
-
E.
servesAsThroughStationFor
Indicates that a station functions as an intermediate (through) stop for a particular service, route, or journey rather than as its starting or ending point.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:18 p.m.