Triple
T34151281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolinian (Amtrak train) |
E876002
|
entity |
| Predicate | previousOperation |
P86262
|
FINISHED |
| Object | 1984–1985 |
—
|
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: 1984–1985 | Statement: [Carolinian (Amtrak train), previousOperation, 1984–1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousOperation Context triple: [Carolinian (Amtrak train), previousOperation, 1984–1985]
-
A.
previousCommand
Indicates that one command directly precedes another in a sequence of executed commands.
-
B.
predecessorOperation
chosen
Indicates that one operation occurs or must be completed before another operation in a defined sequence.
-
C.
previousRecord
Indicates that one record directly precedes another in an ordered sequence of records.
-
D.
previousMode
Indicates that one mode directly precedes another in a sequence or state transition.
-
E.
previousOperatorUntil
Indicates that one operator or action remained in effect up to a certain point in time, immediately before another specified operator or condition became applicable.
- 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_69f349abaa508190a820f206620efddc |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
Created at: May 1, 2026, 1:54 a.m.