Triple
T23924086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Double |
E602296
|
entity |
| Predicate | eliminationGame |
P119136
|
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: [The Double, eliminationGame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliminationGame Context triple: [The Double, eliminationGame, true]
-
A.
loserElimination
Indicates that the entity identified as the loser in a competition, game, or contest is removed or disqualified from further participation.
-
B.
divisionGame
Indicates a competitive interaction where one entity divides or is divided by another according to specific rules or objectives, as in a game based on division operations.
-
C.
typeOfElimination
Indicates the specific method or process by which something is removed, discarded, or ruled out from consideration.
-
D.
gameOfDeath
chosen
Indicates a relationship where an entity is involved in, associated with, or characterized by a lethal contest, challenge, or deadly event.
-
E.
teamEliminationMechanism
Indicates the method or rule by which a team is removed or knocked out from a competition or process.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1abd148190a8393418ed965019 |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:42 p.m.