Triple
T14511823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siad Barre |
E340414
|
entity |
| Predicate | regimeCharacterizedAs |
P114528
|
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: [Siad Barre, regimeCharacterizedAs, authoritarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimeCharacterizedAs Context triple: [Siad Barre, regimeCharacterizedAs, authoritarian]
-
A.
regimeDescription
Indicates that an entity provides a textual characterization or explanation of a particular regime, system, or governing arrangement.
-
B.
regimeDefinedBy
Indicates that a particular regime is characterized, specified, or determined by another entity or set of rules.
-
C.
regimeName
Indicates that a particular name or label is assigned to a specific regime.
-
D.
recognizesRegime
Indicates that one entity formally acknowledges the legitimacy or authority of another entity’s governing regime.
-
E.
historicalRegime
Indicates that one entity functioned as a governing regime or ruling authority over another entity during a specific historical period.
- F. None of above. chosen
Provenance (4 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a6c6054819086b4c0ce1d83fdc5 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:21 a.m.