Triple
T30148209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celebrity Poker Showdown |
E766312
|
entity |
| Predicate | includesHandAnalysis |
P62814
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Celebrity Poker Showdown, includesHandAnalysis, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesHandAnalysis Context triple: [Celebrity Poker Showdown, includesHandAnalysis, true]
-
A.
hasAnalysis
chosen
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
B.
hasHand
Indicates that an entity possesses or is equipped with a hand (or hands) as part of its body or structure.
-
C.
handType
Indicates the specific configuration or category of a hand involved in the relationship or action (e.g., left/right hand, dominant/non-dominant, or type of hand gesture).
-
D.
keyHandInvolves
Indicates that a key hand action or event involves a particular participant, object, or entity as part of that interaction.
-
E.
handCondition
Indicates the state or quality of a hand, such as its health, functionality, or any specific condition affecting it.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a005be4615c8190a710ab704a46c564 |
completed | May 10, 2026, 10:20 a.m. |
| PD | Predicate disambiguation | batch_6a005b8b1cc08190850a392761b84e74 |
completed | May 10, 2026, 10:18 a.m. |
Created at: April 29, 2026, 7:19 p.m.