Triple
T1952972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Othello |
E42199
|
entity |
| Predicate | notableSymbolAssociated |
P1481
|
FINISHED |
| Object | handkerchief |
—
|
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: handkerchief | Statement: [Othello, notableSymbolAssociated, handkerchief]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSymbolAssociated Context triple: [Othello, notableSymbolAssociated, handkerchief]
-
A.
notablyAssociatedWith
chosen
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
D.
notableElement
Indicates that an entity has a component, feature, or part that is especially significant, prominent, or noteworthy in relation to it.
-
E.
notableTarget
Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
- 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_69a8870eea088190a38781990812a9bc |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3501d108190bc5cb23f53db4411 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff3eda88190b643994cb4dfb8df |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.