Triple
T26617664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David R. Ellis |
E668105
|
entity |
| Predicate | stuntPerformerIn |
P161053
|
FINISHED |
| Object | The Blues Brothers |
—
|
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: The Blues Brothers | Statement: [David R. Ellis, stuntPerformerIn, The Blues Brothers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stuntPerformerIn Context triple: [David R. Ellis, stuntPerformerIn, The Blues Brothers]
-
A.
hasStuntDouble
Indicates that one entity serves as a stunt double who performs dangerous or physically demanding actions on behalf of another entity.
-
B.
leadActorPerformedOwnStunts
Indicates that the lead actor personally carried out the stunts in the production rather than using a stunt double.
-
C.
stuntCoordinatorOn
chosen
Indicates that one entity serves as the stunt coordinator responsible for designing and overseeing stunts on a particular production or project involving another entity.
-
D.
heroPerformsFor
Indicates that a hero carries out an action or performance for the benefit, entertainment, or service of another entity.
-
E.
hasStunts
Indicates that one entity performs, includes, or is associated with stunt actions for another entity or context.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 2:19 a.m.