Triple
T37459100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightbomb |
E930872
|
entity |
| Predicate | roleInDeck |
—
|
GENERATED |
| Object | mass removal |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDeck Context triple: [Lightbomb, roleInDeck, mass removal]
-
A.
roleInDominion
Indicates that an entity holds a specific role, position, or function within a particular dominion, realm, or sphere of authority.
-
B.
roleInGameplay
chosen
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
C.
roleInDiceGame
Indicates the specific function or position an entity holds within the context of a dice game (e.g., shooter, dealer, scorer).
-
D.
roleInRepertoire
Indicates that an entity serves a specific role or function within a larger repertoire, collection, or set of items.
-
E.
primaryRoleInDominion
Indicates that the subject holds the main or most important functional role within the specified dominion, domain, or sphere of authority.
- F. None of above.
Provenance (1 batch)
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. |
Created at: May 3, 2026, 4:17 p.m.