Triple
T17890996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas hold 'em poker (in the 2006 film) |
E447313
|
entity |
| Predicate | cardDeckType |
P4066
|
FINISHED |
| Object | standard 52-card deck |
—
|
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 52-card deck | Statement: [Texas hold 'em poker (in the 2006 film), cardDeckType, standard 52-card deck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cardDeckType Context triple: [Texas hold 'em poker (in the 2006 film), cardDeckType, standard 52-card deck]
-
A.
cardSetType
Indicates the classification relationship that specifies what type or category a given card set belongs to.
-
B.
hasDeckType
chosen
Indicates that an entity possesses or is associated with a specific type or category of deck.
-
C.
cardType
Indicates the classification or category assigned to a card within a given system or context.
-
D.
cardClass
Indicates the classification or category to which a given card belongs within a defined card system or schema.
-
E.
cardGameAssociatedWith
Indicates that there is a relationship of association between a card game and another entity, such as a person, place, event, or concept.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7948888190b59ddc7061d13e84 |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.