Triple
T16391558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Parliament 1983–1987 |
E398063
|
entity |
| Predicate | enactedPolicy |
P172
|
FINISHED |
| Object | Thatcherite economic reforms |
—
|
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: Thatcherite economic reforms | Statement: [UK Parliament 1983–1987, enactedPolicy, Thatcherite economic reforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enactedPolicy Context triple: [UK Parliament 1983–1987, enactedPolicy, Thatcherite economic reforms]
-
A.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
B.
implementedPolicy
chosen
Indicates that a particular policy has been put into effect or carried out by an entity.
-
C.
enactedFor
Indicates that an action, rule, or measure is formally established or put into effect on behalf of, or for the benefit of, a particular entity or group.
-
D.
enactedAfter
Indicates that one enactment event occurred later in time than another enactment event.
-
E.
declaredPolicy
Indicates that an entity has formally stated or announced a specific policy or course of action.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e326436ce881909f0f3899b8d931aa |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.