Triple
T29655524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nerazim |
E750252
|
entity |
| Predicate | psionicDiscipline |
P167570
|
FINISHED |
| Object | Void-based psionics |
—
|
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: Void-based psionics | Statement: [Nerazim, psionicDiscipline, Void-based psionics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: psionicDiscipline Context triple: [Nerazim, psionicDiscipline, Void-based psionics]
-
A.
heldSpiritualPower
Indicates that an entity possessed or maintained spiritual or supernatural power in relation to another entity or context.
-
B.
hasRitualFocus
Indicates that an entity is associated with or directed toward a particular object, practice, or element that serves as the central focus of a ritual.
-
C.
typeOfMagic
Indicates that one entity is a specific category, school, or kind of magic associated with another entity.
-
D.
primarySpirit
Indicates that one entity is the main or most fundamental spiritual essence associated with another entity.
-
E.
mentalElement
Indicates that one entity is a mental component, state, or aspect that participates in, underlies, or contributes to another entity, such as a cognitive process, attitude, or psychological condition.
- 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_69f66f274ba08190bcdbdfeccf4af09d |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:55 p.m.