Triple
T8425631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Showdown |
E198978
|
entity |
| Predicate | dramaticIntensity |
P21486
|
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: [Showdown, dramaticIntensity, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticIntensity Context triple: [Showdown, dramaticIntensity, high]
-
A.
hasDramaticTone
chosen
Indicates that something (such as a work, scene, or expression) is characterized by a heightened, intense, or emotionally charged tone.
-
B.
dramaticFunction
Indicates the role or purpose that something serves within the structure or progression of a dramatic work or narrative.
-
C.
dramaticImportance
Indicates that one entity holds significant narrative or emotional weight or impact in relation to another within a dramatic or storytelling context.
-
D.
hasDramaticStyle
Indicates that an entity employs or is characterized by a theatrical, emotionally intense, or striking manner of expression or presentation.
-
E.
hasDramaticElements
Indicates that something contains features or qualities characteristic of drama, such as heightened emotion, tension, or conflict.
- 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_69ca8313c99081909a5c6d83b91de5b3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb85a2871081908a4093838fc93b5a |
completed | March 31, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69cb70d7ea348190aafbf8ca02b7b7d5 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:07 p.m.