Triple
T4529103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilikum Crossing |
E106249
|
entity |
| Predicate | openedToTransit |
P57265
|
FINISHED |
| Object | 2015-09-12 |
—
|
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: 2015-09-12 | Statement: [Tilikum Crossing, openedToTransit, 2015-09-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedToTransit Context triple: [Tilikum Crossing, openedToTransit, 2015-09-12]
-
A.
openedToRailTraffic
Indicates that a rail line, track, or related infrastructure has begun operating and is officially available for use by train traffic.
-
B.
openedAsMBTAStation
Indicates that an entity began operation specifically as an MBTA station at a particular time.
-
C.
openedAsBusTunnelStation
Indicates that a station was originally opened for service as part of a bus tunnel system rather than as a conventional rail or metro station.
-
D.
openedToRoadTraffic
Indicates that something, such as a structure or route, has begun allowing regular use by vehicles or road users.
-
E.
openedRouteThrough
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd5779593081908593537b9239e01b |
completed | March 20, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69bd521cf77c819083852de3094d1377 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:03 p.m.