Triple
T30556924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franklin, Massachusetts |
E777722
|
entity |
| Predicate | hasRailTerminusRole |
P26272
|
FINISHED |
| Object | outer terminus of MBTA Franklin Line |
—
|
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: outer terminus of MBTA Franklin Line | Statement: [Franklin, Massachusetts, hasRailTerminusRole, outer terminus of MBTA Franklin Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailTerminusRole Context triple: [Franklin, Massachusetts, hasRailTerminusRole, outer terminus of MBTA Franklin Line]
-
A.
hasRailwayStationRole
Indicates that an entity holds or is assigned a specific functional role or capacity within the operation or management of a railway station.
-
B.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
C.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
D.
connectsToRailStation
Indicates that one entity has a direct link, route, or access connection to a rail station.
-
E.
railLineTerminus
chosen
Indicates that a rail line ends or terminates at the specified location or station.
- 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_69f2249ed41c8190b175170ecfd6e1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: April 29, 2026, 8:20 p.m.