Triple
T30870254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Desdemona’s handkerchief |
E786318
|
entity |
| Predicate | givenToCharacter |
P170810
|
FINISHED |
| Object | Desdemona |
—
|
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: Desdemona | Statement: [Desdemona’s handkerchief, givenToCharacter, Desdemona]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givenToCharacter Context triple: [Desdemona’s handkerchief, givenToCharacter, Desdemona]
-
A.
givenByCharacter
Indicates that something (such as an item, information, or assistance) is provided or handed over by a particular character.
-
B.
sungToCharacter
Indicates that one entity performs singing directed toward or in the presence of another character.
-
C.
refersToCharacter
Indicates that one entity makes reference to, mentions, or points to a specific character as its subject.
-
D.
dedicatedToCharacter
Indicates that something (such as a work, item, or effort) is formally devoted or addressed in honor of a specific character.
-
E.
representedByCharacter
Indicates that one entity is depicted, symbolized, or personified by a particular character in a work or medium.
- F. None of above. chosen
Provenance (4 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_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:47 p.m.