Triple
T26359632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bure Valley Railway |
E660164
|
entity |
| Predicate | predecessorLineClosed |
P169545
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Bure Valley Railway, predecessorLineClosed, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorLineClosed Context triple: [Bure Valley Railway, predecessorLineClosed, 1982]
-
A.
openedAsPredecessor
Indicates that one entity was opened or began operation as the predecessor to another entity, which later replaced or succeeded it.
-
B.
predecessorStatus
Indicates that one entity’s status is determined by, or directly follows from, the status of a preceding entity in a sequence or process.
-
C.
predecessorControl
Indicates that one entity has control or authority over another entity that precedes it in a sequence, process, or hierarchy.
-
D.
predecessorRelationship
Indicates that one entity comes before another in an ordered sequence, chain, or lineage, serving as its prior or earlier counterpart.
-
E.
predecessorStateOf
Indicates that one state occurs immediately before and leads into another state in a sequence or process.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 26, 2026, 10:50 p.m.