Triple
T37460391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thaddius |
E930901
|
entity |
| Predicate | gameMechanicTheme |
P39812
|
FINISHED |
| Object | polarity-based damage bonus |
—
|
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: polarity-based damage bonus | Statement: [Thaddius, gameMechanicTheme, polarity-based damage bonus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameMechanicTheme Context triple: [Thaddius, gameMechanicTheme, polarity-based damage bonus]
-
A.
gameplayMechanic
chosen
Indicates a relationship where one entity functions as a rule, system, or interactive feature that defines how another entity can be played or operated within a game.
-
B.
gameTheme
Indicates the central subject, style, or conceptual focus that characterizes a game.
-
C.
gameDesignSpecialty
Indicates that one entity has a particular area of specialization or focus within the field of game design in relation to another entity.
-
D.
gameFeatures
Indicates that a game includes or offers a particular element, characteristic, or functionality.
-
E.
gameModeDesign
Indicates that one entity defines or specifies the rules, structure, or configuration of a particular game mode 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_69f76ec1a1148190b0a961f188d621b0 |
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.