Triple
T34863402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altmer |
E1004943
|
entity |
| Predicate | gameplayBonus |
P181936
|
FINISHED |
| Object | +50 magicka in The Elder Scrolls V: Skyrim |
—
|
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: +50 magicka in The Elder Scrolls V: Skyrim | Statement: [Altmer, gameplayBonus, +50 magicka in The Elder Scrolls V: Skyrim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplayBonus Context triple: [Altmer, gameplayBonus, +50 magicka in The Elder Scrolls V: Skyrim]
-
A.
bingoBonus
Indicates that an entity receives or is associated with a bonus specifically awarded in the context of a bingo game or bingo-related activity.
-
B.
hasWonBonus
Indicates that an entity has received or been awarded a bonus, typically as a result of meeting certain conditions or achieving specific performance.
-
C.
bonusCategory
Indicates the classification or type of bonus associated with an entity or transaction.
-
D.
MagicWins
Indicates that one entity achieves victory over another through the use of magic or supernatural powers.
-
E.
hasBonusWorld
Indicates that an entity includes, unlocks, or is associated with an additional bonus world beyond its main content.
- F. None of above. chosen
Provenance (4 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f782f416c081908bdd9b1ad456f0e2 |
completed | May 3, 2026, 5:16 p.m. |
Created at: May 3, 2026, 4 p.m.