Triple
T37458771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piloted Sky Golem |
E930864
|
entity |
| Predicate | summonsOnDeath |
P26125
|
FINISHED |
| Object | random 4-Cost minion |
—
|
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: random 4-Cost minion | Statement: [Piloted Sky Golem, summonsOnDeath, random 4-Cost minion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summonsOnDeath Context triple: [Piloted Sky Golem, summonsOnDeath, random 4-Cost minion]
-
A.
summoned
chosen
Indicates that one entity has called forth, invoked, or ordered the appearance of another entity, typically through authority, command, or supernatural means.
-
B.
summonedAt
Indicates the time or place at which an entity is called, invoked, or brought into presence, typically by another agent or process.
-
C.
completionAfterDeathOf
Indicates that one event, process, or work is completed only after the death of a specified person.
-
D.
summonedIn
Indicates that one entity is called forth, invoked, or brought into presence within the context, location, or event represented by another entity.
-
E.
movementAfterDeath
Indicates a movement or relocation that occurs after an entity has died or ceased living.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.