Triple
T17076213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Two |
E414353
|
entity |
| Predicate | playMechanism |
P39812
|
FINISHED |
| Object | players must play a higher combination than the previous play or pass |
—
|
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: players must play a higher combination than the previous play or pass | Statement: [Big Two, playMechanism, players must play a higher combination than the previous play or pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playMechanism Context triple: [Big Two, playMechanism, players must play a higher combination than the previous play or pass]
-
A.
launchMechanism
Indicates the mechanism or system used to initiate or propel a launch of an object or process.
-
B.
gameplayMechanic
chosen
Indicates a relationship where one entity functions as a rule, system, or interactive feature that defines how another entity can be played or operated within a game.
-
C.
soundMechanism
Indicates a relationship where one entity produces, transmits, or enables the production of sound for another entity or context.
-
D.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
E.
playIn
Indicates that an entity participates or performs in a particular event, context, or location (such as a game, match, or venue).
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc559388190b685504cca6ed62b |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.