Triple
T30716291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | new-democratic revolution |
E782030
|
entity |
| Predicate | economicProgram |
P35538
|
FINISHED |
| Object | land reform |
—
|
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: land reform | Statement: [new-democratic revolution, economicProgram, land reform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: economicProgram Context triple: [new-democratic revolution, economicProgram, land reform]
-
A.
hasEconomicProgram
Indicates that an entity possesses, implements, or is associated with a specific economic plan, policy framework, or set of economic measures.
-
B.
economicPolicyType
Indicates the classification of an economic policy according to its general type or category (e.g., fiscal, monetary, trade).
-
C.
economicPolicyWing
Indicates a relationship where an entity functions as the economic policy division or unit within a larger organization or structure.
-
D.
economicPolicyArea
Indicates the specific domain or sector of economic policy to which an action, measure, or issue is related.
-
E.
politicalProgramIncludes
chosen
Indicates that a political program contains, encompasses, or explicitly incorporates a particular policy, measure, or component.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 29, 2026, 8:35 p.m.