Triple
T36293399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Region |
E893293
|
entity |
| Predicate | subsequentDivisionReplacedBy |
P14054
|
FINISHED |
| Object | sectorisation of British Rail |
—
|
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: sectorisation of British Rail | Statement: [Eastern Region, subsequentDivisionReplacedBy, sectorisation of British Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentDivisionReplacedBy Context triple: [Eastern Region, subsequentDivisionReplacedBy, sectorisation of British Rail]
-
A.
successorDivision
chosen
Indicates that one division is the organizational successor that continues or replaces the role, functions, or identity of another division.
-
B.
divisionRenamedTo
Indicates that an organizational division has changed its name to a new specified name.
-
C.
divisionOccurredUnder
Indicates that a particular division event took place under the authority, jurisdiction, or context of a specified entity or condition.
-
D.
divisionSince
Indicates that one entity has been divided or split from another starting at a specific point in time.
-
E.
divisionOccurred
Indicates that one entity has been separated into two or more distinct parts or groups through a division event.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.