Triple
T29487829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derren Brown: Russian Roulette |
E747978
|
entity |
| Predicate | complaintsTopic |
P171815
|
FINISHED |
| Object | alleged endangerment of life |
—
|
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: alleged endangerment of life | Statement: [Derren Brown: Russian Roulette, complaintsTopic, alleged endangerment of life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complaintsTopic Context triple: [Derren Brown: Russian Roulette, complaintsTopic, alleged endangerment of life]
-
A.
complainsAbout
Indicates that one entity expresses dissatisfaction, criticism, or grievances regarding another entity or situation.
-
B.
topicOfReports
Indicates that something serves as the main subject or focus of one or more reports.
-
C.
handlesComplaintsOn
Indicates that one entity is responsible for receiving, managing, or resolving complaints related to another entity.
-
D.
complainedTo
Indicates that one entity expressed dissatisfaction, criticism, or a grievance directly to another entity.
-
E.
complaintsProcedure
Indicates the formal process or mechanism through which complaints are submitted, handled, and resolved.
- F. None of above. chosen
Provenance (4 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_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 28, 2026, 4:10 p.m.