Triple
T26277904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | post-communist Hungary |
E660624
|
entity |
| Predicate | economicReform |
P87187
|
FINISHED |
| Object | price liberalization |
—
|
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: price liberalization | Statement: [post-communist Hungary, economicReform, price liberalization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicReform Context triple: [post-communist Hungary, economicReform, price liberalization]
-
A.
keyEconomicReformer
Indicates that an entity plays a leading or pivotal role in initiating, driving, or shaping significant economic reforms.
-
B.
economicTransition
Indicates a change in an entity’s economic system, structure, or status from one state or model to another.
-
C.
economicPolicyWing
Indicates a relationship where an entity functions as the economic policy division or unit within a larger organization or structure.
-
D.
economicPolicyOutcome
Indicates the resulting economic conditions, effects, or consequences that arise from implementing a particular economic policy.
-
E.
economicPolicyArea
chosen
Indicates the specific domain or sector of economic policy to which an action, measure, or issue is related.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 26, 2026, 9:57 p.m.