Triple
T31041603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariel DuBois |
E791009
|
entity |
| Predicate | hasPsychicAbility |
P150714
|
FINISHED |
| Object | precognitive dreams |
—
|
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: precognitive dreams | Statement: [Ariel DuBois, hasPsychicAbility, precognitive dreams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPsychicAbility Context triple: [Ariel DuBois, hasPsychicAbility, precognitive dreams]
-
A.
hasChildWithPsychicAbility
Indicates that an entity has at least one child who possesses a psychic or supernatural mental ability.
-
B.
featuresPsychicCharacter
chosen
Indicates that the subject includes or involves a character who possesses psychic or telepathic abilities.
-
C.
believedToHaveAbility
Indicates that one entity is thought or assumed to possess a particular capability or power, without asserting that the ability is actually verified.
-
D.
psionicDiscipline
Indicates that an entity practices, specializes in, or is associated with a particular psionic discipline or mental power tradition.
-
E.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694fa62308190aa7ca49724a6cb06 |
completed | May 3, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:59 p.m.