Triple
T30994069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Man's Hand (poker hand) |
E789744
|
entity |
| Predicate | associatedWithGameVariant |
P141416
|
FINISHED |
| Object | five-card stud |
—
|
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: five-card stud | Statement: [Dead Man's Hand (poker hand), associatedWithGameVariant, five-card stud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithGameVariant Context triple: [Dead Man's Hand (poker hand), associatedWithGameVariant, five-card stud]
-
A.
associatedWithGame
Indicates that there is a relationship or connection between an entity and a particular game.
-
B.
associatedWithGameNumber
Indicates a relationship where something is linked or tied to a specific game identified by its number.
-
C.
hasCardGameVariant
chosen
Indicates that one game is a variation or modified form of another card game.
-
D.
relatedGame
Indicates that one game has a notable connection or association with another game, such as shared content, themes, or series.
-
E.
associatedWithPlayers
Indicates a relationship in which one or more players are connected, linked, or otherwise involved with the referenced entity.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:56 p.m.