Triple
T20007418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velvet |
E494493
|
entity |
| Predicate | hasDramaticPlot |
P21484
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Velvet, hasDramaticPlot, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDramaticPlot Context triple: [Velvet, hasDramaticPlot, true]
-
A.
hasDramaticElements
chosen
Indicates that something contains features or qualities characteristic of drama, such as heightened emotion, tension, or conflict.
-
B.
hasDramaticStructure
Indicates that something possesses or follows a specific dramatic structure, such as an organized sequence of narrative or theatrical elements (e.g., exposition, climax, resolution).
-
C.
hasDramaticPurpose
Indicates that something serves a specific dramatic function or role within a narrative or performance.
-
D.
hasDramaticProduction
Indicates that an entity is associated with or features a specific dramatic production (such as a play, performance, or staged work).
-
E.
hasDramaticStyle
Indicates that an entity employs or is characterized by a theatrical, emotionally intense, or striking manner of expression or presentation.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a648a88190853ee741edcf6ca2 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.