Triple
T9473935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Light (Next to Normal) |
E228462
|
entity |
| Predicate | dramaticArcRole |
P36856
|
FINISHED |
| Object | closure without complete cure |
—
|
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: closure without complete cure | Statement: [Light (Next to Normal), dramaticArcRole, closure without complete cure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dramaticArcRole Context triple: [Light (Next to Normal), dramaticArcRole, closure without complete cure]
-
A.
dramaticRole
Indicates that one entity serves as a character or part played by another entity within a dramatic or theatrical work.
-
B.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
C.
characterArcElement
chosen
Indicates that one element is a component or stage within a character’s overall developmental arc or transformation.
-
D.
characterArc
Indicates the developmental journey or transformation a character undergoes over the course of a narrative.
-
E.
dramaticCharacter
Indicates that one entity is a character or role that appears within the dramatic work, performance, or narrative represented by the other entity.
- 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_69ca847162c48190b079076c9595513c |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7ff23aec8190b5341eb9bd816a43 |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55f01b081908dc0f12eaa45f832 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:54 p.m.