Triple
T23284185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pot-Limit Omaha |
E588943
|
entity |
| Predicate | isCommonlyPlayedStakes |
P78239
|
FINISHED |
| Object | mid-stakes cash games |
—
|
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: mid-stakes cash games | Statement: [Pot-Limit Omaha, isCommonlyPlayedStakes, mid-stakes cash games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonlyPlayedStakes Context triple: [Pot-Limit Omaha, isCommonlyPlayedStakes, mid-stakes cash games]
-
A.
isTypicallyPlayed
chosen
Indicates that an activity, game, or sport is commonly engaged in or performed by a particular type of participant or group.
-
B.
typeOfStake
Indicates the specific kind or category of stake or ownership interest that one entity holds in another.
-
C.
typicallyPlays
Indicates that an entity is most commonly or habitually associated with playing a particular role, instrument, position, or type of game.
-
D.
isHighStakes
Indicates that the situation, event, or decision involves significant risk, consequences, or potential impact, making the outcome particularly critical.
-
E.
isUsedToPlay
Indicates that something serves as an instrument, tool, or medium for engaging in a game, sport, or other form of play.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196454b4c8190a797537ce8912241 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:58 p.m.