Triple
T13740351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British coal industry |
E330069
|
entity |
| Predicate | privatisedIn |
P23781
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [British coal industry, privatisedIn, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privatisedIn Context triple: [British coal industry, privatisedIn, 1990s]
-
A.
privatizedOn
chosen
Indicates the date or point in time when an entity transitioned from public or state ownership/control to private ownership/control.
-
B.
privatizedInto
Indicates that a previously public or state-owned entity has been transferred into private ownership or control, typically becoming a private company or organization.
-
C.
privatisationContext
Indicates the context, conditions, or circumstances under which a privatisation process or action takes place.
-
D.
implementedPrivatization
Indicates that an entity carried out or put into effect the process of transferring ownership or control from public to private hands.
-
E.
privatizationMethod
Indicates the specific process or mechanism by which ownership or control of a public asset, service, or enterprise is transferred to private entities.
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0206a4b88190a60914e2b43e54f9 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.