Triple
T17890963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas hold 'em poker (in the 2006 film) |
E447313
|
entity |
| Predicate | purposeForHero |
P79
|
FINISHED |
| Object | to bankrupt Le Chiffre |
—
|
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: to bankrupt Le Chiffre | Statement: [Texas hold 'em poker (in the 2006 film), purposeForHero, to bankrupt Le Chiffre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeForHero Context triple: [Texas hold 'em poker (in the 2006 film), purposeForHero, to bankrupt Le Chiffre]
-
A.
purpose
chosen
Indicates that one entity exists, is done, or is used in order to achieve, support, or serve the goal, function, or intended outcome of another entity.
-
B.
missionOfAntagonist
Indicates the primary goal, plan, or objective that the antagonist is actively pursuing.
-
C.
findsPurposeThrough
Indicates that one entity derives its sense of purpose, meaning, or fulfillment through its relationship with or actions involving another entity.
-
D.
heroDepicted
Indicates that one entity is portrayed or represented as a hero in relation to another entity.
-
E.
reasonForTribute
Indicates the underlying cause, justification, or circumstance that explains why a tribute is given.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7948888190b59ddc7061d13e84 |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.