Triple
T37459500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troggzor the Earthinator |
E930881
|
entity |
| Predicate | summonedMinionInstanceOf |
P189389
|
FINISHED |
| Object | Hearthstone minion token |
—
|
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: Hearthstone minion token | Statement: [Troggzor the Earthinator, summonedMinionInstanceOf, Hearthstone minion token]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summonedMinionInstanceOf Context triple: [Troggzor the Earthinator, summonedMinionInstanceOf, Hearthstone minion token]
-
A.
summonedMinionType
chosen
Indicates that one entity has summoned or created another entity specifically as a minion of a given type.
-
B.
summonedMinionName
Indicates that one entity has summoned or called forth a specific minion, identified by its name.
-
C.
summonedMinionText
Indicates that one entity has called forth or created another entity to serve as its minion.
-
D.
summonedMinionCost
Indicates the resource cost required to summon a minion in the given context.
-
E.
tribeOfSummonedMinion
Indicates that a summoned minion belongs to or is categorized under a particular tribe or creature type.
- 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_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:17 p.m.