Triple
T34451605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Variorum edition of Othello |
E884381
|
entity |
| Predicate | editorLifespan |
P585
|
FINISHED |
| Object | 1833–1912 |
—
|
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: 1833–1912 | Statement: [Variorum edition of Othello, editorLifespan, 1833–1912]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: editorLifespan Context triple: [Variorum edition of Othello, editorLifespan, 1833–1912]
-
A.
authorLifespanContext
Indicates the temporal or historical context of an author’s life span in relation to other events, periods, or entities.
-
B.
lifespan
chosen
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
C.
editorEndTime
Indicates the time at which an entity’s role or activity as an editor comes to an end.
-
D.
lifespanType
Indicates the type or category of lifespan associated with an entity, such as whether it is finite, indefinite, or of a particular defined duration.
-
E.
subjectLifespanEnd
Indicates the point in time or event at which the subject’s life comes to an end.
- 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.