Triple
T14519975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dead Pool |
E340624
|
entity |
| Predicate | featuresFictionalGame |
P65304
|
FINISHED |
| Object | celebrity death pool |
—
|
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: celebrity death pool | Statement: [The Dead Pool, featuresFictionalGame, celebrity death pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresFictionalGame Context triple: [The Dead Pool, featuresFictionalGame, celebrity death pool]
-
A.
featuresGame
chosen
Indicates that something (such as a platform, service, or collection) includes or presents a particular game as part of its offerings.
-
B.
featuresFictionalProgram
Indicates that a work includes or presents a fictional program (such as a TV show, software, or in-universe broadcast) as part of its content.
-
C.
featuresFictionalSport
Indicates that a work includes or showcases a fictional sport as part of its content or setting.
-
D.
gameFeatures
Indicates that a game includes or offers a particular element, characteristic, or functionality.
-
E.
featuresFictionalTechnology
Indicates that an entity includes, depicts, or makes use of imagined or speculative technology that does not exist in reality.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de9a70b15c81908773633e989ef704 |
completed | April 14, 2026, 7:50 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.