Triple
T29654880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Templar |
E750237
|
entity |
| Predicate | isPsionic |
P150714
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [High Templar, isPsionic, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPsionic Context triple: [High Templar, isPsionic, yes]
-
A.
hasChildWithPsychicAbility
Indicates that an entity has at least one child who possesses a psychic or supernatural mental ability.
-
B.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
-
C.
featuresPsychicCharacter
chosen
Indicates that the subject includes or involves a character who possesses psychic or telepathic abilities.
-
D.
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.
-
E.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
- 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_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. |
Created at: April 28, 2026, 6:54 p.m.