Triple
T30148198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celebrity Poker Showdown |
E766312
|
entity |
| Predicate | hasTournamentChips |
P181242
|
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, hasTournamentChips, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTournamentChips Context triple: [Celebrity Poker Showdown, hasTournamentChips, true]
-
A.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
-
B.
hasTournamentLevel
Indicates that an entity participates in or is classified by a specific competitive or organizational level within a tournament structure.
-
C.
hasTournamentType
Indicates that a tournament is classified as belonging to a specific type or category (e.g., league, knockout, friendly).
-
D.
hasBettingRounds
Indicates that an activity, event, or game includes one or more distinct phases during which participants can place or adjust bets.
-
E.
hasTournamentRecord
Indicates that an entity possesses a documented performance or results record in a specific tournament or set of tournaments.
- F. None of above. chosen
Provenance (4 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_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 29, 2026, 7:19 p.m.