Triple
T28747721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British electricity supply industry |
E731422
|
entity |
| Predicate | nationalisationDate |
P18594
|
FINISHED |
| Object | 1948 |
—
|
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: 1948 | Statement: [British electricity supply industry, nationalisationDate, 1948]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalisationDate Context triple: [British electricity supply industry, nationalisationDate, 1948]
-
A.
nationalisedOn
Indicates the date or point in time when an entity was taken into state ownership or control by a national government.
-
B.
nationalisationYear
chosen
Indicates the year in which an entity was taken into state ownership or control through nationalisation.
-
C.
nationalizationBy
Indicates the process by which a government takes private or non-state-owned assets, industries, or enterprises into public or state ownership.
-
D.
nationalised
Indicates that control or ownership of an entity has been transferred from private or non-state hands to the government or state.
-
E.
nationalizationReason
Indicates the reason or justification for which an entity is nationalized by a state or government.
- 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_69f043ecb5c081909ec9da1172d68ece |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 6:06 a.m.