Triple
T6510344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christine |
E150110
|
entity |
| Predicate | powersOrigin |
P61281
|
FINISHED |
| Object | unexplained clairvoyant ability |
—
|
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: unexplained clairvoyant ability | Statement: [Christine, powersOrigin, unexplained clairvoyant ability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powersOrigin Context triple: [Christine, powersOrigin, unexplained clairvoyant ability]
-
A.
sourceOfPower
chosen
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
B.
powers
Indicates that one entity supplies or provides the energy, authority, or driving force that enables another entity to function or operate.
-
C.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
D.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
-
E.
createsPower
Indicates that one entity is the source or generator of power, energy, or influence for another entity or system.
- 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_69c687ef291081909d437f035eef1cda |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c69f398f10819096342f3646cefcc2 |
completed | March 27, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:43 p.m.