Triple
T9053373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic People's Congresses |
E216938
|
entity |
| Predicate | claimedDecisionMakingMode |
P39758
|
FINISHED |
| Object | direct democracy |
—
|
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: direct democracy | Statement: [Basic People's Congresses, claimedDecisionMakingMode, direct democracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedDecisionMakingMode Context triple: [Basic People's Congresses, claimedDecisionMakingMode, direct democracy]
-
A.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
B.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
C.
decisionStyle
chosen
Indicates the characteristic way an entity approaches, processes, and makes decisions in a given context.
-
D.
makesDecisionBy
Indicates that one entity determines or chooses an outcome, course of action, or judgment by means of another entity, method, or process.
-
E.
decisiveFor
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7a71a9d88190949ef9dc6816d6ab |
completed | April 1, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:10 p.m.