Triple
T5650506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Blake |
E124494
|
entity |
| Predicate | hasDramaticStyle |
P65429
|
FINISHED |
| Object | realism |
—
|
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: realism | Statement: [Christopher Blake, hasDramaticStyle, realism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDramaticStyle Context triple: [Christopher Blake, hasDramaticStyle, realism]
-
A.
hasDramaticTone
Indicates that something (such as a work, scene, or expression) is characterized by a heightened, intense, or emotionally charged tone.
-
B.
hasDramaticElements
Indicates that something contains features or qualities characteristic of drama, such as heightened emotion, tension, or conflict.
-
C.
hasDramaticProduction
Indicates that an entity is associated with or features a specific dramatic production (such as a play, performance, or staged work).
-
D.
dramaticCharacter
Indicates that one entity is a character or role that appears within the dramatic work, performance, or narrative represented by the other entity.
-
E.
dramaticFunction
Indicates the role or purpose that something serves within the structure or progression of a dramatic work or narrative.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d4ca788190b20168b20cb1d030 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2274b48190b2ef57ed728f785c |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0727bc8190b16e9a669c04b4dd |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:42 p.m.