Triple
T2332224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desdemona |
E44226
|
entity |
| Predicate | centralThemeInvolvement |
P6627
|
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: [Desdemona, centralThemeInvolvement, jealousy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralThemeInvolvement Context triple: [Desdemona, centralThemeInvolvement, jealousy]
-
A.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
hasCentralTheme
chosen
Indicates that one entity serves as the primary or dominant theme or subject matter of another entity.
-
C.
oftenInvolvedWith
Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
-
D.
centralThemeContribution
Indicates that one entity contributes significantly to shaping, supporting, or expressing the central theme of another entity.
-
E.
centerType
Indicates the classification or category of a center (e.g., type of facility, institution, or hub) associated with an 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:51 p.m.