Triple
T11544222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tavern Brawl |
E273741
|
entity |
| Predicate | firstWinReward |
P14849
|
FINISHED |
| Object | one Classic card pack in many brawls |
—
|
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: one Classic card pack in many brawls | Statement: [Tavern Brawl, firstWinReward, one Classic card pack in many brawls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstWinReward Context triple: [Tavern Brawl, firstWinReward, one Classic card pack in many brawls]
-
A.
winnerReceives
chosen
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
B.
firstWinner
Indicates that the subject is the entity who achieved first place or victory in the referenced event or competition.
-
C.
firstBlockReward
Indicates the initial reward amount granted for producing or validating the very first block in a blockchain or similar sequential ledger.
-
D.
monetaryReward
Indicates that one entity provides or promises a payment of money to another as compensation, incentive, or prize.
-
E.
firstTitleForWinner
Indicates that the associated title is the first title ever won by the specified winner.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e1d754819089f3b6be3404fa0b |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.