Triple
T34334720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abdelazer, or The Moor's Revenge |
E881112
|
entity |
| Predicate | writtenByWoman |
P178886
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Abdelazer, or The Moor's Revenge, writtenByWoman, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenByWoman Context triple: [Abdelazer, or The Moor's Revenge, writtenByWoman, true]
-
A.
actuallyWrittenBy
Indicates that the specified work was in fact authored by the given entity, possibly correcting or overriding a previously assumed or credited author.
-
B.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
C.
writtenAgainst
Indicates that a written work (such as a document, article, or statement) is composed in opposition to, or as a critique or complaint about, a particular target.
-
D.
notWrittenBy
Indicates that a specified work or content is explicitly not authored or created by a given entity.
-
E.
createdByWritersOf
Indicates that something (such as a work, character, or concept) was created by the writers of a specified work or series.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71782422c81908196d5e4a610cb1a |
completed | May 3, 2026, 9:38 a.m. |
Created at: May 1, 2026, 1:58 a.m.