Triple
T23083250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Poker Tour |
E575533
|
entity |
| Predicate | typicalGameVariant |
P141416
|
FINISHED |
| Object | no-limit Texas hold 'em |
—
|
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: no-limit Texas hold 'em | Statement: [World Poker Tour, typicalGameVariant, no-limit Texas hold 'em]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGameVariant Context triple: [World Poker Tour, typicalGameVariant, no-limit Texas hold 'em]
-
A.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
B.
playsSevensVariant
Indicates that an entity participates in or engages in a sevens variant of a game or sport.
-
C.
hasCardGameVariant
chosen
Indicates that one game is a variation or modified form of another card game.
-
D.
isTypicallyPlayed
Indicates that an activity, game, or sport is commonly engaged in or performed by a particular type of participant or group.
-
E.
typicalTimeControl
Indicates the usual or standard time control under which an activity, event, or process is typically conducted.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da304548190ab7a421c1ded0eb6 |
completed | April 29, 2026, 4:48 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 3:56 p.m.