Triple
T32036433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Designated Mourner |
E818106
|
entity |
| Predicate | stageDirector |
P173796
|
FINISHED |
| Object | David Hare |
—
|
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: David Hare | Statement: [The Designated Mourner, stageDirector, David Hare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageDirector Context triple: [The Designated Mourner, stageDirector, David Hare]
-
A.
stageDirectionType
Indicates the specific kind or category of stage direction associated with a performance element or action.
-
B.
stageDirectionName
Indicates the specific label or term used to identify a particular stage direction within a performance or script.
-
C.
stageDirectionDescription
Indicates a textual description of how an action, movement, or expression should be performed or presented within a staged or scripted context.
-
D.
stageDesigner
Indicates that one entity is responsible for designing or creating the stage or set for a performance or event in relation to another entity.
-
E.
directorOfScene
Indicates that one entity serves as the director responsible for the creative and practical oversight of a particular scene.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ba1733408190af579d93a7946508 |
completed | May 3, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:18 a.m.