Triple
T8829104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Union Terminal |
E210086
|
entity |
| Predicate | passengerRailServiceEnded |
P27833
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Cleveland Union Terminal, passengerRailServiceEnded, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passengerRailServiceEnded Context triple: [Cleveland Union Terminal, passengerRailServiceEnded, 1970s]
-
A.
railServiceEnded
chosen
Indicates that a previously operating rail service has been discontinued or terminated.
-
B.
ferryServiceEnded
Indicates that a previously operating ferry service between locations has been discontinued or terminated.
-
C.
railServicesTo
Indicates that rail transportation services operate from one location to another specified destination.
-
D.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
E.
airportPassengerServiceEndedAt
Indicates that the provision of passenger-related services at an airport concluded at a specific time or event.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc604c52a48190807e46c15e3c1558 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:47 p.m.