Triple
T34451596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Variorum edition of Othello |
E884381
|
entity |
| Predicate | textualSourcesCollated |
P175043
|
FINISHED |
| Object | First Quarto of 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: First Quarto of Othello | Statement: [Variorum edition of Othello, textualSourcesCollated, First Quarto of Othello]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualSourcesCollated Context triple: [Variorum edition of Othello, textualSourcesCollated, First Quarto of Othello]
-
A.
textSources
Indicates that one entity serves as a source or origin for the text content associated with another entity.
-
B.
textCollectionSource
chosen
Indicates that a text collection originates from, or is derived from, a particular source.
-
C.
literarySource
Indicates that one entity serves as the written or literary origin, reference, or basis for another entity.
-
D.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
E.
primarySourcesDiscussed
Indicates that the primary source materials are examined, analyzed, or discussed in relation to the subject.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2 a.m.