Triple
T37664475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Guardian |
E937789
|
entity |
| Predicate | canBeSummonedByCommand |
P100266
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Elder Guardian, canBeSummonedByCommand, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSummonedByCommand Context triple: [Elder Guardian, canBeSummonedByCommand, Yes]
-
A.
canBeSummonedByPlayer
chosen
Indicates that the entity is capable of being brought into the game world or into action through a summoning action performed by a player.
-
B.
canSummonToken
Indicates that an entity has the ability to create or bring forth a specific token into play or existence.
-
C.
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.
-
D.
summonedMinionText
Indicates that one entity has called forth or created another entity to serve as its minion.
-
E.
summonedMinionKeyword
Indicates that one entity has been brought into play or created as a subordinate or controlled minion 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff6fba1a5c8190a660279a6271d785 |
completed | May 9, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69ff6f59388c8190a7d6ab7bc7705bc0 |
completed | May 9, 2026, 5:31 p.m. |
Created at: May 3, 2026, 4:18 p.m.