Triple
T37465596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World of Warcraft Darkmoon Faire |
E931025
|
entity |
| Predicate | givesBuff |
P2188
|
FINISHED |
| Object | Whee! experience and reputation buff |
—
|
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: Whee! experience and reputation buff | Statement: [World of Warcraft Darkmoon Faire, givesBuff, Whee! experience and reputation buff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesBuff Context triple: [World of Warcraft Darkmoon Faire, givesBuff, Whee! experience and reputation buff]
-
A.
hasBonusMaterial
Indicates that an item includes additional supplementary content beyond its main or primary material.
-
B.
buffType
Indicates the type or category of beneficial or detrimental status effect applied to an entity.
-
C.
hasBenefit
chosen
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
D.
givesJewelsTo
Indicates that one entity transfers or presents jewels to another entity.
-
E.
supportsBonus
Indicates that one entity provides or enables an additional benefit, reward, or bonus for 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.