Triple
T35510598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Megaton |
E1026275
|
entity |
| Predicate | playerKarmaEffect |
P159162
|
FINISHED |
| Object | disarming bomb grants positive karma |
—
|
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: disarming bomb grants positive karma | Statement: [Megaton, playerKarmaEffect, disarming bomb grants positive karma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerKarmaEffect Context triple: [Megaton, playerKarmaEffect, disarming bomb grants positive karma]
-
A.
scoreEffect
Indicates the impact or change that an action, event, or condition has on a score or scoring outcome.
-
B.
gameplayImpact
Indicates how one element in a game affects the mechanics, difficulty, or overall experience of playing that game.
-
C.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
D.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
E.
reputationEffect
chosen
Indicates how one entity’s actions or characteristics influence the perceived reputation or standing of 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:04 p.m.