Triple
T23284115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No-Limit Texas Hold'em |
E588942
|
entity |
| Predicate | hasForcedBet |
P151671
|
FINISHED |
| Object | small blind |
—
|
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: small blind | Statement: [No-Limit Texas Hold'em, hasForcedBet, small blind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasForcedBet Context triple: [No-Limit Texas Hold'em, hasForcedBet, small blind]
-
A.
hasToteBetting
Indicates that an entity offers or is associated with pari-mutuel (tote) betting services or facilities.
-
B.
hasForceStrength
Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
-
C.
wagerAmount
Indicates the specific sum of money or value that is staked or risked in a bet or wager between parties.
-
D.
hasHighestForceNumber
Indicates that the subject entity possesses the greatest force value or ranking compared to all other relevant entities in the given context.
-
E.
hasParticipantForce
Indicates that an event or action involves a participant specifically in the role of exerting or applying force.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:58 p.m.