Triple
T37461217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukla, Tyrant of the Vale |
E930920
|
entity |
| Predicate | cardTextRaw |
P187875
|
FINISHED |
| Object | Battlecry: Add 2 Bananas to your hand. |
—
|
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: Battlecry: Add 2 Bananas to your hand. | Statement: [Mukla, Tyrant of the Vale, cardTextRaw, Battlecry: Add 2 Bananas to your hand.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardTextRaw Context triple: [Mukla, Tyrant of the Vale, cardTextRaw, Battlecry: Add 2 Bananas to your hand.]
-
A.
cardText
chosen
Indicates that one entity is the textual content displayed on a card associated with another entity.
-
B.
cardTextType
Indicates the type or category of textual content associated with a card (e.g., title, body text, caption, or label).
-
C.
cardExample
Indicates that something is an illustrative or sample instance of a card (such as a prototype, demo, or example card) rather than a primary or production card.
-
D.
cardVariant
Indicates that one card is a specific version or variation of another base card.
-
E.
cardName
Indicates that one entity is the name or title assigned to a specific card 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_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:17 p.m.