Triple
T14476889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breath |
E358995
|
entity |
| Predicate | usesSoundAsDramaticElement |
P73293
|
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: [Breath, usesSoundAsDramaticElement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSoundAsDramaticElement Context triple: [Breath, usesSoundAsDramaticElement, true]
-
A.
hasDramaticTone
Indicates that something (such as a work, scene, or expression) is characterized by a heightened, intense, or emotionally charged tone.
-
B.
hasDramaticTechnique
chosen
Indicates that one entity employs, features, or is characterized by a particular dramatic technique associated with another entity.
-
C.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
-
D.
hasSound
Indicates that an entity produces, emits, or is associated with a particular sound.
-
E.
dramaticSource
Indicates that something serves as the origin or basis for a dramatic work, performance, or representation.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9248edb48190a74eb032aeaac027 |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.