Triple
T5487077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Shore and Michigan Southern Railway |
E123608
|
entity |
| Predicate | dateCeasedToExist |
P17487
|
FINISHED |
| Object | 1914 |
—
|
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: 1914 | Statement: [Lake Shore and Michigan Southern Railway, dateCeasedToExist, 1914]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateCeasedToExist Context triple: [Lake Shore and Michigan Southern Railway, dateCeasedToExist, 1914]
-
A.
ceaseToExistDecisionDate
Indicates the date on which a formal decision was made that something will cease to exist or be terminated.
-
B.
existedUntil
chosen
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
-
C.
dateOfAbandonment
Indicates the specific date on which something (such as a place, project, or object) was formally or effectively abandoned or discontinued.
-
D.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
E.
dateAbolished
Indicates the date on which something (such as an institution, law, practice, or position) was officially ended or abolished.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd93e5d0f08190a6cc9fc408b7c5bb |
completed | March 20, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69bd91a73b148190a865243536a4fe76 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:10 p.m.