Triple
T35105890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | manuscripts of Vox Clamantis |
E1013150
|
entity |
| Predicate | subjectWorkAuthor |
P194435
|
FINISHED |
| Object | John Gower |
—
|
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: John Gower | Statement: [manuscripts of Vox Clamantis, subjectWorkAuthor, John Gower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectWorkAuthor Context triple: [manuscripts of Vox Clamantis, subjectWorkAuthor, John Gower]
-
A.
subjectOfWorkBy
Indicates that one entity is the main topic or focus of a work (such as a book, article, or artwork) created by another entity.
-
B.
basedOnWorkAuthorAssociatedWith
Indicates that one entity is derived from or related to a work whose author is associated with another specified entity.
-
C.
associatedWithAuthorWork
Indicates a relationship where an author is connected to a work they created, contributed to, or are otherwise credited for.
-
D.
authorOfParentWork
Indicates that one entity is the author of a work that serves as the parent or source for another related work.
-
E.
publisherOfWorkAboutSubject
Indicates that an entity is the publisher of a work whose content is about a specified subject.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: May 3, 2026, 4:01 p.m.