Triple
T29654886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Templar |
E750237
|
entity |
| Predicate | controlsPower |
P192644
|
FINISHED |
| Object | Khala psionic energies (in early lore) |
—
|
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: Khala psionic energies (in early lore) | Statement: [High Templar, controlsPower, Khala psionic energies (in early lore)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsPower Context triple: [High Templar, controlsPower, Khala psionic energies (in early lore)]
-
A.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
B.
powerHandling
Indicates how an entity manages, controls, or withstands the amount of power or energy applied to it or passing through it.
-
C.
powerOption
Indicates that one entity provides or specifies a particular power-related configuration or choice available to another entity.
-
D.
modeOfPower
Indicates the type or method of power or energy by which an entity operates or is driven.
-
E.
enablingPowerFor
Indicates that one entity provides the capability or authority that allows another entity to perform a specific function, action, or role.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: April 28, 2026, 6:54 p.m.