Triple
T37541598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death (Warcraft cosmology) |
E933337
|
entity |
| Predicate | channeledBy |
P188233
|
FINISHED |
| Object | necromancers |
—
|
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: necromancers | Statement: [Death (Warcraft cosmology), channeledBy, necromancers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: channeledBy Context triple: [Death (Warcraft cosmology), channeledBy, necromancers]
-
A.
replacedByChannel
Indicates that one communication channel has been superseded or substituted by another channel.
-
B.
ownedChannel
Indicates that one entity possesses ownership or control over a particular channel.
-
C.
canChannel
Indicates that one entity is able to direct, transmit, or route something (such as information, energy, or resources) through another entity or medium.
-
D.
basedOnChannel
Indicates that something is determined, derived, or decided according to a particular channel as its basis or reference.
-
E.
channelLining
Indicates the presence or application of a protective or functional lining along the interior surface of a channel or conduit.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba5ee00fc81909be7b947a3f95034 |
completed | May 6, 2026, 8:34 p.m. |
Created at: May 3, 2026, 4:17 p.m.