Triple
T1620092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MBTA bus route 57 |
E35009
|
entity |
| Predicate | isMajorTransitCorridor |
P24235
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MBTA bus route 57, isMajorTransitCorridor, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorTransitCorridor Context triple: [MBTA bus route 57, isMajorTransitCorridor, yes]
-
A.
hasMajorRailCorridor
Indicates that a location or region is traversed by a primary, high-capacity railway route used for significant passenger or freight transport.
-
B.
isMajorInterchangeFor
Indicates that one location functions as a primary hub where multiple routes or lines connect or transfer between each other for another location.
-
C.
hasMajorRailLinksTo
Indicates that there are significant railway connections or routes between two locations.
-
D.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
E.
majorUrbanCorridor
chosen
Indicates a primary transportation route that connects significant urban areas and supports major flows of people, goods, or services between them.
- 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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf4a0ef748190ae52b9656474c0ef |
completed | March 6, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69a907c731808190a1d998155041b3c1 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.