Triple
T31105452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor of the Known Universe |
E792779
|
entity |
| Predicate | usesInstrumentOfControl |
P49579
|
FINISHED |
| Object | Sardaukar terror troops |
—
|
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 terror troops | Statement: [Emperor of the Known Universe, usesInstrumentOfControl, Sardaukar terror troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInstrumentOfControl Context triple: [Emperor of the Known Universe, usesInstrumentOfControl, Sardaukar terror troops]
-
A.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
B.
usedToControl
chosen
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
C.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
-
D.
usedControl
Indicates that one entity exercised or applied a control mechanism or method over another entity or process.
-
E.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
- 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_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:03 p.m.