Triple
T6263713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Rail first-generation DMUs |
E140360
|
entity |
| Predicate | continuedInServiceOn |
P69802
|
FINISHED |
| Object | rural routes |
—
|
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: rural routes | Statement: [British Rail first-generation DMUs, continuedInServiceOn, rural routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedInServiceOn Context triple: [British Rail first-generation DMUs, continuedInServiceOn, rural routes]
-
A.
inService
Indicates that an entity is currently active, operational, or available for use in its intended role or function.
-
B.
inServiceFrom
Indicates the time or event from which an entity (such as a service, system, or asset) begins being operationally active or officially in use.
-
C.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
-
D.
commissionedInService
Indicates that an entity was formally brought into active service or duty within a particular organization, role, or context.
-
E.
serviceContinuationEra
Indicates the historical or temporal period during which a service continues to operate or remain in effect.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69c05707d5408190a1d0fd80414ad957 |
completed | March 22, 2026, 8:54 p.m. |
Created at: March 22, 2026, 4:25 p.m.