Triple
T14967154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Downtown Seattle Transit Tunnel |
E373218
|
entity |
| Predicate | busServiceEndDate |
P6603
|
FINISHED |
| Object | 2019-03-23 |
—
|
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: 2019-03-23 | Statement: [Downtown Seattle Transit Tunnel, busServiceEndDate, 2019-03-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busServiceEndDate Context triple: [Downtown Seattle Transit Tunnel, busServiceEndDate, 2019-03-23]
-
A.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
B.
cityServedUntil
Indicates the city that was served by an entity (such as a service, route, or facility) up to a specified end time or date.
-
C.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
D.
railServiceEnded
Indicates that a previously operating rail service has been discontinued or terminated.
-
E.
notableFlightEndDate
Indicates the date on which a notable or significant flight concluded or reached its endpoint.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6e2fdcc8190bffe603db3388736 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:47 a.m.