Triple
T5559995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advanced Passenger Train |
E145741
|
entity |
| Predicate | commercialServiceEnd |
P21869
|
FINISHED |
| Object | mid-1980s |
—
|
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: mid-1980s | Statement: [Advanced Passenger Train, commercialServiceEnd, mid-1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialServiceEnd Context triple: [Advanced Passenger Train, commercialServiceEnd, mid-1980s]
-
A.
commercialService
Indicates a relationship where one entity provides a paid, profit-oriented service to another entity.
-
B.
originalServiceEnded
chosen
Indicates that a previously existing or initial service has come to an end or has been terminated.
-
C.
officeEnded
Indicates that a person’s term in an office or position has concluded at a specified time or under certain conditions.
-
D.
commercialAccess
Indicates that an entity is permitted to use or access something for commercial or profit-generating purposes.
-
E.
commercialOutcome
Indicates that an action, event, or relationship results in, or is associated with, a specific commercial or financial consequence.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020167afc8190b0c518907cd0d99b |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.