Triple
T37459279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron Juggernaut |
E930876
|
entity |
| Predicate | burrowingMineEffect |
P187910
|
FINISHED |
| Object | Deal 10 damage to the drawing hero |
—
|
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: Deal 10 damage to the drawing hero | Statement: [Iron Juggernaut, burrowingMineEffect, Deal 10 damage to the drawing hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burrowingMineEffect Context triple: [Iron Juggernaut, burrowingMineEffect, Deal 10 damage to the drawing hero]
-
A.
burrowingMineDamage
chosen
Indicates that damage is caused by a mine that moves or burrows underground before detonating.
-
B.
burrowingMineType
Indicates that the subject is associated with or classified as a type of mine that moves or operates by burrowing into a medium (such as soil, rock, or another substrate).
-
C.
burrowingMineZone
Indicates a zone where burrowing mines are placed, active, or expected to operate.
-
D.
burrowUse
Indicates that an entity makes use of a burrow, typically as a shelter, nesting site, or refuge.
-
E.
burrowSystem
Indicates that one entity is a system or network of burrows associated with another entity.
- 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_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.