Triple
T30870289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desdemona’s handkerchief |
E786318
|
entity |
| Predicate | themeLinkedTo |
P124132
|
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’s handkerchief, themeLinkedTo, jealousy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeLinkedTo Context triple: [Desdemona’s handkerchief, themeLinkedTo, jealousy]
-
A.
styleLinkedTo
Indicates a relationship where one style is associated with, derived from, or otherwise connected to another style.
-
B.
associatedThemeElements
chosen
Indicates a relationship where certain elements are linked to, or grouped under, a particular theme as its related components.
-
C.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
D.
symbolLinked
Indicates a relationship where one symbol is connected or associated with another symbol, typically to show reference, correspondence, or linkage between them.
-
E.
hasThemeRelationship
Indicates a relationship where one entity is thematically related to, or centered around, another entity as its main subject or topic.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691d0b19c819085b47b20f55e39cb |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:47 p.m.