Triple
T27811392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allegiant General Pryde |
E702526
|
entity |
| Predicate | militaryStyle |
P172803
|
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: [Allegiant General Pryde, militaryStyle, authoritarian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryStyle Context triple: [Allegiant General Pryde, militaryStyle, authoritarian]
-
A.
militarySize
Indicates the total number of personnel in a military force, typically including active-duty members and sometimes reserves.
-
B.
militaryDerivative
Indicates that one entity is derived from, adapted from, or developed based on another entity within a military context (such as technology, doctrine, or organization).
-
C.
militaryDiscipline
Indicates the enforcement or practice of rules, order, and conduct within a military context.
-
D.
militaryBacked
Indicates that one entity is supported, protected, or sustained by the military power or armed forces of another entity.
-
E.
militaryUniformUsage
Indicates that an entity uses, wears, or is associated with a specific type or style of military uniform.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 27, 2026, 5:42 p.m.