Triple
T29487819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derren Brown: Russian Roulette |
E747978
|
entity |
| Predicate | locationOfFinalStunt |
P12513
|
FINISHED |
| Object | Jersey |
—
|
NE NERFINISHED |
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: Jersey | Statement: [Derren Brown: Russian Roulette, locationOfFinalStunt, Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfFinalStunt Context triple: [Derren Brown: Russian Roulette, locationOfFinalStunt, Jersey]
-
A.
finalsLocation
chosen
Indicates the place where the final stage or concluding event of something (such as a competition or process) takes place.
-
B.
formerFinishLocation
Indicates that an entity was previously the finish location of an event or activity, but no longer holds that status.
-
C.
climaxLocation
Indicates the place or setting where the most intense or pivotal moment of an event, narrative, or process occurs.
-
D.
finalConcertLocation
Indicates the location where a concert or performance ultimately takes place, especially after any changes or planning stages.
-
E.
lastLocation
Indicates the most recent known place or position where an entity was located.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a00315632a8819092290f455babd7ee |
completed | May 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_6a002f54a0dc81909b0e54c5e110e67c |
completed | May 10, 2026, 7:10 a.m. |
Created at: April 28, 2026, 4:10 p.m.