Triple
T23284120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No-Limit Texas Hold'em |
E588942
|
entity |
| Predicate | handRankingSystem |
P12314
|
FINISHED |
| Object | standard high poker hand rankings |
—
|
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: standard high poker hand rankings | Statement: [No-Limit Texas Hold'em, handRankingSystem, standard high poker hand rankings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handRankingSystem Context triple: [No-Limit Texas Hold'em, handRankingSystem, standard high poker hand rankings]
-
A.
squareRank
Indicates that one entity has a square (second-power) relationship to the rank or position value of another entity.
-
B.
hasRankingStrength
Indicates the relative strength or priority of an entity’s ranking compared to others in a given ordering or evaluation.
-
C.
hasNumberOfHands
Indicates the specific count of hands that an entity possesses.
-
D.
hasRankingCategory
chosen
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
-
E.
handicap
Indicates that one entity imposes or experiences a disadvantage, constraint, or limiting condition in relation to another entity or context.
- 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.