Triple
T11796145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christine Hartmann |
E280510
|
entity |
| Predicate | emotionalRoleInPlot |
P65521
|
FINISHED |
| Object | focus of emotional drama |
—
|
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: focus of emotional drama | Statement: [Christine Hartmann, emotionalRoleInPlot, focus of emotional drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emotionalRoleInPlot Context triple: [Christine Hartmann, emotionalRoleInPlot, focus of emotional drama]
-
A.
emotionalRole
chosen
Indicates a relationship where one entity holds a particular emotional significance, function, or impact in relation to another entity.
-
B.
protagonistLover
Indicates that one entity is the romantic partner or love interest of the story’s protagonist.
-
C.
narrativeRoleInSeries
Indicates the specific narrative function or role an entity plays within a particular series or serialized work.
-
D.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
E.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a1cda0819092d66a82fd882786 |
completed | April 10, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.