Triple
T31954605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act 1, Scene 1 of Othello |
E815869
|
entity |
| Predicate | featuresOffstageCharacter |
P202657
|
FINISHED |
| Object | Othello |
—
|
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: Othello | Statement: [Act 1, Scene 1 of Othello, featuresOffstageCharacter, Othello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresOffstageCharacter Context triple: [Act 1, Scene 1 of Othello, featuresOffstageCharacter, Othello]
-
A.
featuresReturningCharacterFrom
Indicates that a work includes the reappearance of a character who previously appeared in the referenced source work.
-
B.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
-
C.
notableTraitOnStage
Indicates that an entity is characterized by a distinctive or noteworthy trait specifically in the context of performing or appearing on stage.
-
D.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
E.
featuresOrphanCharacter
Indicates that the subject includes or presents a character who is an orphan within its content or narrative.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_6a00a74afb3c8190a274bf6681950aa3 |
completed | May 10, 2026, 3:42 p.m. |
Created at: May 1, 2026, 12:08 a.m.