Triple
T398859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penn Central Transportation Company |
E9233
|
entity |
| Predicate | ceasedRailOperations |
P6603
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [Penn Central Transportation Company, ceasedRailOperations, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedRailOperations Context triple: [Penn Central Transportation Company, ceasedRailOperations, 1976]
-
A.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
B.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
C.
operatedCarriageWorksAt
Indicates that a person or organization managed and ran the operations of a carriage works at a particular location or during a specific period.
-
D.
decommissionedReason
Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
-
E.
railwayCompany
Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
- 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_69a2e8004cb88190b92ed1add6abf41a |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ec8d0ca881909d786e8eed9b6748 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.