Triple
T30870264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desdemona’s handkerchief |
E786318
|
entity |
| Predicate | manipulatedByCharacter |
P149659
|
FINISHED |
| Object | Iago |
—
|
NE NERFINISHED |
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: Iago | Statement: [Desdemona’s handkerchief, manipulatedByCharacter, Iago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: manipulatedByCharacter Context triple: [Desdemona’s handkerchief, manipulatedByCharacter, Iago]
-
A.
manipulatedBy
Indicates that an entity is controlled, influenced, or operated by another entity, often in a deliberate or strategic manner.
-
B.
operatedByCharacter
Indicates that an operation, action, or process is carried out or controlled by a specific character.
-
C.
exploitedByCharacter
chosen
Indicates that a character takes unfair advantage of, manipulates, or otherwise uses another entity for their own benefit.
-
D.
modifiedByCharacter
Indicates that something has been altered or influenced through the actions or behavior of a particular character.
-
E.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed 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_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.