Triple
T37459100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightbomb |
E930872
|
entity |
| Predicate | roleInDeck |
P100032
|
FINISHED |
| Object | mass removal |
—
|
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: mass removal | Statement: [Lightbomb, roleInDeck, mass removal]
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 (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_6a021706e21c81909b83e2b4d9c4130c |
completed | May 11, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_6a0216861214819097d2177755bc19d7 |
completed | May 11, 2026, 5:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.