Triple
T2191079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poglavnik |
E49861
|
entity |
| Predicate | associatedWithRegimeType |
P24598
|
FINISHED |
| Object | 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: one-party state | Statement: [Poglavnik, associatedWithRegimeType, one-party state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRegimeType Context triple: [Poglavnik, associatedWithRegimeType, one-party state]
-
A.
associatedWithRegime
Indicates a relationship where an entity is linked or connected to a particular regime, such as a political, governmental, or ruling system.
-
B.
belongsToRegimenType
chosen
Indicates that something is associated with or classified under a specific regimen type.
-
C.
regulatoryType
Indicates the specific kind or category of regulatory control, rule, or oversight that applies in the given relationship.
-
D.
supportedRegime
Indicates that an entity provided assistance, endorsement, or backing to a particular political regime or government in power.
-
E.
registryType
Indicates the specific category or classification of a registry that an entity is associated with or recorded in.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf3f5e008190beda3ce5d77209e0 |
completed | March 7, 2026, 6:01 a.m. |
| PD | Predicate disambiguation | batch_69abbda52328819089c7ab111bebb0ca |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.