Triple
T37463130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Living Mana |
E930967
|
entity |
| Predicate | tribeOfSummonedMinions |
P189398
|
FINISHED |
| Object | Treant |
—
|
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: Treant | Statement: [Living Mana, tribeOfSummonedMinions, Treant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribeOfSummonedMinions Context triple: [Living Mana, tribeOfSummonedMinions, Treant]
-
A.
tribeOfSummonedMinion
chosen
Indicates that a summoned minion belongs to or is categorized under a particular tribe or creature type.
-
B.
summonedMinionType
Indicates that one entity has summoned or created another entity specifically as a minion of a given type.
-
C.
summonedMinionCost
Indicates the resource cost required to summon a minion in the given context.
-
D.
maxCostOfDrawnMinions
Indicates the maximum cost among all minions that are drawn in the context of this action or effect.
-
E.
summonedIn
Indicates that one entity is called forth, invoked, or brought into presence within the context, location, or event represented by 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:17 p.m.