Triple
T23083251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Poker Tour |
E575533
|
entity |
| Predicate | alsoCoversGameVariant |
P13946
|
FINISHED |
| Object | pot-limit Omaha |
—
|
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: pot-limit Omaha | Statement: [World Poker Tour, alsoCoversGameVariant, pot-limit Omaha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoCoversGameVariant Context triple: [World Poker Tour, alsoCoversGameVariant, pot-limit Omaha]
-
A.
hasCardGameVariant
Indicates that one game is a variation or modified form of another card game.
-
B.
alsoCovers
chosen
Indicates that something extends its scope or applicability to include an additional subject, area, or case beyond what was originally covered.
-
C.
playsVariantOf
Indicates that one entity performs, uses, or engages with a version or adaptation of another entity, typically differing in form, rules, or style from the original.
-
D.
supportsGames
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
E.
rulesVariantOf
Indicates that one set of rules is a modified or alternative version derived from another set of rules.
- 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.