Triple
T30148205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celebrity Poker Showdown |
E766312
|
entity |
| Predicate | includesFinalTable |
P202153
|
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, includesFinalTable, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFinalTable Context triple: [Celebrity Poker Showdown, includesFinalTable, true]
-
A.
includesFinal
Indicates that one entity contains or encompasses another entity as its concluding or last part.
-
B.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
-
C.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
D.
includesRight
Indicates that one entity contains, encompasses, or grants a particular right to another entity.
-
E.
includesMap
Indicates that one entity contains or incorporates another entity in the form of a map or mapping structure.
- 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_6a005b2e0a9c819081c6f7ccbef49ff8 |
completed | May 10, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a005a8bcde88190ace2bc0215e26430 |
completed | May 10, 2026, 10:14 a.m. |
| PDg | Predicate description generation | batch_6a005b2cdbc881908b433623e3252df5 |
completed | May 10, 2026, 10:17 a.m. |
Created at: April 29, 2026, 7:19 p.m.