Triple
T23284177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pot-Limit Omaha |
E588943
|
entity |
| Predicate | bettingRounds |
P68186
|
FINISHED |
| Object | preflop |
—
|
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: preflop | Statement: [Pot-Limit Omaha, bettingRounds, preflop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bettingRounds Context triple: [Pot-Limit Omaha, bettingRounds, preflop]
-
A.
bettingOdds
Indicates the likelihood or probability of a particular outcome in a bet, typically expressed as numerical odds set for wagering.
-
B.
endingInPlay
Indicates that an event, sequence, or process concludes while a play or gameplay is still in progress.
-
C.
titleClinchedRoundsRemaining
Indicates the number of rounds remaining in a competition or season at the point when a title or championship has been mathematically secured.
-
D.
racesOn
Indicates that one entity participates in a race or competitive running event that takes place on or along another entity (such as a track, course, or surface).
-
E.
roundsStructure
chosen
Indicates that one entity defines or specifies the organization, sequence, or format of rounds within a process, event, or system.
- 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.