Triple
T1674529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seaboard Coast Line Railroad |
E36199
|
entity |
| Predicate | transferToAmtrakYear |
P9945
|
FINISHED |
| Object | 1971 |
—
|
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: 1971 | Statement: [Seaboard Coast Line Railroad, transferToAmtrakYear, 1971]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferToAmtrakYear Context triple: [Seaboard Coast Line Railroad, transferToAmtrakYear, 1971]
-
A.
transitionYear
Indicates the specific year in which a change, shift, or transition from one state, condition, or phase to another occurs.
-
B.
introducedByAmtrak
Indicates that something (such as a service, policy, feature, or change) was initiated, launched, or brought into use by Amtrak.
-
C.
travelsToYear
Indicates that an entity moves or is transported from its original time to a specified calendar year.
-
D.
annualRidership
Indicates the total number of passengers who use a transportation service over the course of one year.
-
E.
takenOverInYear
chosen
Indicates that one entity assumed control or ownership of another entity in a specified calendar year.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab272a653481908f48aa1eed5de8a4 |
completed | March 6, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69aa61b2f6288190b2348ef7d7e4672d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.