Triple
T16836431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Region of British Railways |
E409292
|
entity |
| Predicate | wasReorganisedInto |
P109886
|
FINISHED |
| Object | sectorisation of British Rail in the 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: sectorisation of British Rail in the 1980s | Statement: [Southern Region of British Railways, wasReorganisedInto, sectorisation of British Rail in the 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasReorganisedInto Context triple: [Southern Region of British Railways, wasReorganisedInto, sectorisation of British Rail in the 1980s]
-
A.
reorganizedAs
Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
-
B.
wasRestructuredInto
chosen
Indicates that an entity underwent an organizational or structural change resulting in it becoming a different, successor entity.
-
C.
reorganizedIn
Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
-
D.
reorganizedDueTo
Indicates that one entity was reorganized as a consequence of, or in response to, another specified factor, event, or condition.
-
E.
laterReorganizedBy
Indicates that an entity was subsequently restructured, reorganized, or reformed by another entity at a later 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b34d49d08190aa62f05d67244584 |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.