Triple
T31895829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liar's Poker |
E814278
|
entity |
| Predicate | describesGame |
P65304
|
FINISHED |
| Object | liar's poker |
—
|
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: liar's poker | Statement: [Liar's Poker, describesGame, liar's poker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesGame Context triple: [Liar's Poker, describesGame, liar's poker]
-
A.
playDescription
Indicates that an entity provides a textual or verbal description of a play, performance, or dramatic work.
-
B.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
C.
featuresGame
chosen
Indicates that something (such as a platform, service, or collection) includes or presents a particular game as part of its offerings.
-
D.
game6Description
Indicates the textual description or summary associated with the sixth game in a sequence or set of games.
-
E.
designedGame
Indicates that one entity is the creator or designer responsible for the conception and development of a particular game.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 30, 2026, 11:58 p.m.