Triple
T7337287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Law No. 43 of 1974 |
E169159
|
entity |
| Predicate | replacedPolicyTrend |
P3140
|
FINISHED |
| Object | state‑led socialist economic model |
—
|
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: state‑led socialist economic model | Statement: [Law No. 43 of 1974, replacedPolicyTrend, state‑led socialist economic model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedPolicyTrend Context triple: [Law No. 43 of 1974, replacedPolicyTrend, state‑led socialist economic model]
-
A.
replacedPolicyApproach
chosen
Indicates that one policy approach has been superseded and taken the place of another policy approach.
-
B.
changePolicy
Indicates that an entity modifies, replaces, or updates an existing policy governing rules, procedures, or behaviors.
-
C.
policyShift
Indicates a change or adjustment in an existing policy, typically reflecting a new direction, priority, or approach.
-
D.
sawPolicyChange
Indicates that an entity observed, experienced, or became aware of a change in policy affecting it or its context.
-
E.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:04 p.m.