Triple
T2110445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emilia (Othello character) |
E42487
|
entity |
| Predicate | themeInvolved |
P30025
|
FINISHED |
| Object | jealousy |
—
|
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: jealousy | Statement: [Emilia (Othello character), themeInvolved, jealousy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeInvolved Context triple: [Emilia (Othello character), themeInvolved, jealousy]
-
A.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
B.
themeFor
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
C.
themeExamples
Indicates that the related entity serves as an example or illustration of the theme expressed by the subject.
-
D.
themedAs
Indicates that something is characterized, styled, or organized according to a particular theme or motif.
-
E.
themeInvolvingCharacter
chosen
Indicates that a theme, motif, or abstract concept centrally involves or is significantly shaped by a particular character.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb024ce88190a30e1320e53b82bc |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.