Triple
T37464910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zzeraku the Warped |
E931009
|
entity |
| Predicate | summonsToken |
P188359
|
FINISHED |
| Object | Nether Drake |
—
|
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: Nether Drake | Statement: [Zzeraku the Warped, summonsToken, Nether Drake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summonsToken Context triple: [Zzeraku the Warped, summonsToken, Nether Drake]
-
A.
canSummonToken
chosen
Indicates that an entity has the ability to create or bring forth a specific token into play or existence.
-
B.
summonsForOpponent
Indicates that one entity initiates or performs a summoning action on behalf of, or targeting, an opposing entity.
-
C.
summoned
Indicates that one entity has called forth, invoked, or ordered the appearance of another entity, typically through authority, command, or supernatural means.
-
D.
summonCount
Indicates the number of times an entity has been summoned or caused to appear.
-
E.
summonedAt
Indicates the time or place at which an entity is called, invoked, or brought into presence, typically by another agent or process.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.