Triple
T20178876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uno |
E492671
|
entity |
| Predicate | actionCardEffect |
P53074
|
FINISHED |
| Object | Skip causes next player to lose a turn |
—
|
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: Skip causes next player to lose a turn | Statement: [Uno, actionCardEffect, Skip causes next player to lose a turn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actionCardEffect Context triple: [Uno, actionCardEffect, Skip causes next player to lose a turn]
-
A.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
B.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
C.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to another entity.
-
D.
notableEffect
Indicates that one entity has a significant impact, consequence, or influence on another entity or situation.
-
E.
awardEffect
Indicates that one entity confers or grants a benefit, recognition, or reward that has a particular impact or consequence on 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668ed07c8819091bd9ffda237a91c |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.