Triple
T33891319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doaker Charles |
E868773
|
entity |
| Predicate | hasStageDirectionAttribute |
P174879
|
FINISHED |
| Object | middle-aged |
—
|
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: middle-aged | Statement: [Doaker Charles, hasStageDirectionAttribute, middle-aged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageDirectionAttribute Context triple: [Doaker Charles, hasStageDirectionAttribute, middle-aged]
-
A.
hasStageDirections
Indicates that a dramatic work or script includes explicit stage directions describing actions, movements, or settings.
-
B.
stageDirectionTrait
chosen
Indicates a characteristic or quality associated with how a stage direction is expressed or performed in a dramatic work.
-
C.
includesFamousStageDirection
Indicates that the subject contains or features a well-known or widely recognized stage direction within it.
-
D.
stageDirectionType
Indicates the specific kind or category of stage direction associated with a performance element or action.
-
E.
stageDirectionName
Indicates the specific label or term used to identify a particular stage direction within a performance or script.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
Created at: May 1, 2026, 1:48 a.m.