Triple
T29736573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tassadar |
E752476
|
entity |
| Predicate | combinesPowerOf |
P102364
|
FINISHED |
| Object | Khalai Templar |
—
|
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: Khalai Templar | Statement: [Tassadar, combinesPowerOf, Khalai Templar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinesPowerOf Context triple: [Tassadar, combinesPowerOf, Khalai Templar]
-
A.
combinesPowers
chosen
Indicates that two or more entities merge their abilities or strengths to produce a unified, often enhanced, effect.
-
B.
enhancesPowersOf
Indicates that one entity increases, amplifies, or strengthens the abilities or powers of another entity.
-
C.
powerBy
Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
-
D.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
E.
strengthenedPowerIn
Indicates that one entity has increased, reinforced, or consolidated its power, influence, or control within a particular context, domain, or location represented by the other entity.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673344cf88190855d66b73e45cb5d |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:45 p.m.