Triple
T37461371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mire Keeper |
E930924
|
entity |
| Predicate | summonedTokenHealth |
P188343
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Mire Keeper, summonedTokenHealth, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summonedTokenHealth Context triple: [Mire Keeper, summonedTokenHealth, 2]
-
A.
summonedMinionHealth
chosen
Indicates the health value of a minion that has been summoned by another entity.
-
B.
summoningSickness
Indicates that an entity is temporarily unable to act or perform certain actions immediately after entering the field or coming under a player’s control.
-
C.
canSummonToken
Indicates that an entity has the ability to create or bring forth a specific token into play or existence.
-
D.
summonedMinionText
Indicates that one entity has called forth or created another entity to serve as its minion.
-
E.
summonCount
Indicates the number of times an entity has been summoned or caused to appear.
- 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_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:17 p.m.