Triple
T8188447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floridian (train) |
E191244
|
entity |
| Predicate | operatorEndDate |
P6603
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [Floridian (train), operatorEndDate, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorEndDate Context triple: [Floridian (train), operatorEndDate, 1979]
-
A.
setsTermEndDateFor
Indicates setting or assigning the end date of a term or period for another entity.
-
B.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
C.
operatedUntil
chosen
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
D.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
E.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4d9f4a488190b39bdc1792646914 |
completed | March 31, 2026, 4:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.