Triple
T37457962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life Tap |
E930845
|
entity |
| Predicate | canBeUsedOncePerTurn |
P149053
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Life Tap, canBeUsedOncePerTurn, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedOncePerTurn Context triple: [Life Tap, canBeUsedOncePerTurn, Yes]
-
A.
canBeUsedOncePer
chosen
Indicates that the associated action or resource is limited to a single use within each specified unit (such as per turn, per day, or per user).
-
B.
isSingleUseItem
Indicates that an item is intended to be used only once before being discarded or rendered unusable.
-
C.
summoningSickness
Indicates that an entity is temporarily unable to act or perform certain actions immediately after entering the field or coming under a player’s control.
-
D.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to another entity.
-
E.
skillUsedFor
Indicates that a particular skill is employed or applied to perform, achieve, or facilitate a specific task, goal, or function.
- 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_69ff16775a9881909d26dbc1f0ef3e1c |
completed | May 9, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_69ff158e61708190a1c581d0d306cfce |
completed | May 9, 2026, 11:07 a.m. |
Created at: May 3, 2026, 4:17 p.m.