Triple
T37460461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sludge Belcher |
E930903
|
entity |
| Predicate | summonedMinionKeyword |
P191848
|
FINISHED |
| Object | Taunt |
—
|
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: Taunt | Statement: [Sludge Belcher, summonedMinionKeyword, Taunt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summonedMinionKeyword Context triple: [Sludge Belcher, summonedMinionKeyword, Taunt]
-
A.
summonedMinionText
Indicates that one entity has called forth or created another entity to serve as its minion.
-
B.
summonedMinionType
Indicates that one entity has summoned or created another entity specifically as a minion of a given type.
-
C.
summonedMinionName
Indicates that one entity has summoned or called forth a specific minion, identified by its name.
-
D.
summonedMinionCost
Indicates the resource cost required to summon a minion in the given context.
-
E.
summoned
Indicates that one entity has called forth, invoked, or ordered the appearance of another entity, typically through authority, command, or supernatural means.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: May 3, 2026, 4:17 p.m.