Triple
T30994063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dead Man's Hand (poker hand) |
E789744
|
entity |
| Predicate | hasCombinationType |
P58402
|
FINISHED |
| Object | two pair |
—
|
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: two pair | Statement: [Dead Man's Hand (poker hand), hasCombinationType, two pair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCombinationType Context triple: [Dead Man's Hand (poker hand), hasCombinationType, two pair]
-
A.
allowsCombination
Indicates that one entity permits or supports being combined or used together with another entity.
-
B.
combinationType
chosen
Indicates how multiple elements are combined or related to each other within a composite structure or operation.
-
C.
isConsideredCombinationOf
Indicates that something is regarded as being formed by or equivalent to a specific combination of other things or components.
-
D.
hasComb
Indicates that an entity possesses or is equipped with a comb.
-
E.
typicalCombinationWith
Indicates that one entity is commonly or characteristically used, found, or occurs together in combination with another 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_6a01b935e3948190a7af37b07938d618 |
completed | May 11, 2026, 11:10 a.m. |
| PD | Predicate disambiguation | batch_6a01b8d198b48190b01e16ac9ce7e7bd |
completed | May 11, 2026, 11:09 a.m. |
Created at: April 29, 2026, 8:56 p.m.