Triple
T37461356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blood of The Ancient One |
E930923
|
entity |
| Predicate | summonedMinionStats |
P188343
|
FINISHED |
| Object | 30/30 (The Ancient One) |
—
|
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: 30/30 (The Ancient One) | Statement: [Blood of The Ancient One, summonedMinionStats, 30/30 (The Ancient One)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summonedMinionStats Context triple: [Blood of The Ancient One, summonedMinionStats, 30/30 (The Ancient One)]
-
A.
summonedMinionText
Indicates that one entity has called forth or created another entity to serve as its minion.
-
B.
summonedMinionHealth
chosen
Indicates the health value of a minion that has been summoned by another entity.
-
C.
summonedMinionCost
Indicates the resource cost required to summon a minion in the given context.
-
D.
summonedMinionName
Indicates that one entity has summoned or called forth a specific minion, identified by its name.
-
E.
summonedMinionType
Indicates that one entity has summoned or created another entity specifically as a minion of a given 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_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.