Triple
T31105443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor of the Known Universe |
E792779
|
entity |
| Predicate | hasMilitaryArm |
P104865
|
FINISHED |
| Object | Sardaukar |
—
|
NE NERFINISHED |
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: Sardaukar | Statement: [Emperor of the Known Universe, hasMilitaryArm, Sardaukar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryArm Context triple: [Emperor of the Known Universe, hasMilitaryArm, Sardaukar]
-
A.
hasArmedForces
chosen
Indicates that an entity possesses or maintains organized military forces under its control.
-
B.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
C.
hasMilitaryText
Indicates that an entity possesses or is associated with a text whose content is military in nature (e.g., about armed forces, warfare, or defense).
-
D.
hasMilitaryAssociation
Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
-
E.
hasMilitarySecurity
Indicates that an entity provides, maintains, or is responsible for military protection or defense for another entity or area.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 29, 2026, 9:03 p.m.