Triple
T9136480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Venice (Othello) |
E219216
|
entity |
| Predicate | literaryRoleType |
P15535
|
FINISHED |
| Object | supporting character |
—
|
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: supporting character | Statement: [Duke of Venice (Othello), literaryRoleType, supporting character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryRoleType Context triple: [Duke of Venice (Othello), literaryRoleType, supporting character]
-
A.
literaryRole
chosen
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
B.
genreRole
Indicates a relationship where an entity holds a specific functional or categorical role within a particular genre.
-
C.
creativeRole
Indicates that an entity holds a specific creative function or responsibility in relation to another entity, such as a work or project.
-
D.
genreOfWorkCharacterIsIn
Indicates the specific genre of the creative work in which a given character appears.
-
E.
cultRole
Indicates that an entity holds a specific role, position, or function within a cult or cult-like group.
- 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8e1dc208190aafe501374ffe65c |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.