Triple
T13617214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pan-American |
E325346
|
entity |
| Predicate | endedServiceWith |
P21869
|
FINISHED |
| Object | formation of Amtrak |
—
|
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: formation of Amtrak | Statement: [Pan-American, endedServiceWith, formation of Amtrak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedServiceWith Context triple: [Pan-American, endedServiceWith, formation of Amtrak]
-
A.
endedFunctionallyWith
Indicates that a process, event, or relationship has effectively concluded in practice, even if it has not been formally or officially terminated.
-
B.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
C.
originalServiceEnded
chosen
Indicates that a previously existing or initial service has come to an end or has been terminated.
-
D.
serviceEnded
Indicates that a previously active service or service relationship has come to an end.
-
E.
endedFor
Indicates that a particular event, state, or process has come to an end for a specified entity or participant.
- 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_69d8076aae28819092cf636190ee5529 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:50 p.m.