Triple
T29284357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swanilda |
E742466
|
entity |
| Predicate | dramaticDemand |
P164245
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Swanilda, dramaticDemand, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticDemand Context triple: [Swanilda, dramaticDemand, high]
-
A.
dramaticRequirement
chosen
Indicates that one entity is necessary or demanded by another in order to create, heighten, or sustain dramatic tension or effect.
-
B.
dramaticAction
Indicates an action or event characterized by heightened emotion, tension, or significance that drives or intensifies a dramatic situation or narrative.
-
C.
dramaticFunction
Indicates the role or purpose that something serves within the structure or progression of a dramatic work or narrative.
-
D.
dramaticFeature
Indicates that one entity possesses or exhibits a notable dramatic characteristic or element in relation to another entity.
-
E.
dramaticTrait
Indicates that an entity possesses a tendency to behave or express itself in an exaggerated, theatrical, or emotionally intense manner.
- 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_69f09121ed8c8190b4cb27be3619c262 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f665191d888190b4ab2c4bbd7725cb |
completed | May 2, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:56 p.m.