Triple
T6263712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail first-generation DMUs |
E140360
|
entity |
| Predicate | continuedInServiceUntil |
P37781
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [British Rail first-generation DMUs, continuedInServiceUntil, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedInServiceUntil Context triple: [British Rail first-generation DMUs, continuedInServiceUntil, 1990s]
-
A.
servedUntil
chosen
Indicates the ending time or date up to which an entity held a position, role, or service.
-
B.
serviceContinuationEra
Indicates the historical or temporal period during which a service continues to operate or remain in effect.
-
C.
remainedInForceUntil
Indicates that a rule, condition, or state continued to be valid or effective up to a specified point in time.
-
D.
managedUntil
Indicates that one entity was responsible for managing or overseeing another entity up to a specific point in time.
-
E.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
- 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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06387fec0819095b47a37b9402aa9 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.