Triple
T3858040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Front for Democracy and Justice |
E90065
|
entity |
| Predicate | partySystemType |
P19538
|
FINISHED |
| Object | de facto one-party state |
—
|
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: de facto one-party state | Statement: [People's Front for Democracy and Justice, partySystemType, de facto one-party state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partySystemType Context triple: [People's Front for Democracy and Justice, partySystemType, de facto one-party state]
-
A.
politicalParty
Indicates that an entity is affiliated with, belongs to, or is a member of a specific political party.
-
B.
partySystemRole
Indicates the specific functional role or capacity that a party assumes within a given system or context.
-
C.
dominantPartySystem
chosen
Indicates a political system in which one party consistently dominates governance over time, despite the presence of other legally allowed parties.
-
D.
partyNumber
Indicates the identifier or ordinal position assigned to a specific party within a multi-party relationship or transaction.
-
E.
partyOfCandidate
Indicates the political party with which a given candidate is affiliated.
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec1e68f88190941c39221486f6ae |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.