Triple
T37460733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kel'Thuzad (card) |
E930909
|
entity |
| Predicate | roleInAdventure |
P140406
|
FINISHED |
| Object | Reward card |
—
|
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: Reward card | Statement: [Kel'Thuzad (card), roleInAdventure, Reward card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAdventure Context triple: [Kel'Thuzad (card), roleInAdventure, Reward card]
-
A.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
B.
roleOfCharacter
chosen
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
C.
roleForProtagonist
Indicates the specific narrative or functional role that an entity plays in relation to the story’s main protagonist.
-
D.
roleInSpearOfDestiny
Indicates that an entity has a specific role or involvement in the context of the Spear of Destiny.
-
E.
roleInFableIII
Indicates that an entity has a specific role or function within the context of the work "Fable III."
- 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_6a021f84715881908e25b6548e7cf62e |
completed | May 11, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_6a021739b7288190a4ca94c04074c78a |
completed | May 11, 2026, 5:51 p.m. |
Created at: May 3, 2026, 4:17 p.m.