Triple
T34620855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GWR Hall Class |
E888996
|
entity |
| Predicate | operatorAfterNationalisation |
P202820
|
FINISHED |
| Object | British Railways |
—
|
NE NERFINISHED |
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: British Railways | Statement: [GWR Hall Class, operatorAfterNationalisation, British Railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAfterNationalisation Context triple: [GWR Hall Class, operatorAfterNationalisation, British Railways]
-
A.
ownedByAfterNationalisation
Indicates that an entity became owned by another entity as a result of a nationalisation process occurring after a specified point in time.
-
B.
region after nationalisation
Indicates that a region is characterized or defined by its status or condition following a process of nationalisation.
-
C.
nationalisedOn
Indicates the date or point in time when an entity was taken into state ownership or control by a national government.
-
D.
nationalisationYear
Indicates the year in which an entity was taken into state ownership or control through nationalisation.
-
E.
ownershipStatusAfterPrivatisation
Indicates the type or state of ownership an entity has after a privatisation process has taken place.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00bf5990e08190a8b633e237656564 |
completed | May 10, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_6a00beef4f5881909b00ac89e6af5902 |
completed | May 10, 2026, 5:22 p.m. |
| PDg | Predicate description generation | batch_6a00bf5899b08190ad012a0879907d65 |
completed | May 10, 2026, 5:24 p.m. |
Created at: May 1, 2026, 2:04 a.m.