Triple
T4369733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reich Protector |
E98865
|
entity |
| Predicate | natureOfRegime |
P220
|
FINISHED |
| Object | authoritarian |
—
|
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: authoritarian | Statement: [Reich Protector, natureOfRegime, authoritarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfRegime Context triple: [Reich Protector, natureOfRegime, authoritarian]
-
A.
typeOfRegimeChange
Indicates a change in the form, structure, or governing system of a political regime, such as transitions between different types of rule or authority.
-
B.
recognizesRegime
Indicates that one entity formally acknowledges the legitimacy or authority of another entity’s governing regime.
-
C.
politicalRegimeEstablished
Indicates that a particular political regime has been formally created and brought into effect in a given place or context.
-
D.
governmentType
chosen
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
E.
regimeDefinedBy
Indicates that a particular regime is characterized, specified, or determined by another entity or set of rules.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352052b388190b02cca9a3b480be4 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.