Triple
T35608041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book I (The Well-Tempered Clavier) |
E1028951
|
entity |
| Predicate | authorOfManuscript |
P63068
|
FINISHED |
| Object | Johann Sebastian Bach |
—
|
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: Johann Sebastian Bach | Statement: [Book I (The Well-Tempered Clavier), authorOfManuscript, Johann Sebastian Bach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorOfManuscript Context triple: [Book I (The Well-Tempered Clavier), authorOfManuscript, Johann Sebastian Bach]
-
A.
associatedWithManuscript
Indicates a relationship in which an entity is linked or connected to a particular manuscript, such as by authorship, reference, inclusion, or relevance.
-
B.
authorOfParentWork
Indicates that one entity is the author of a work that serves as the parent or source for another related work.
-
C.
subjectWorkAuthor
Indicates that the subject is the author or creator of the referenced work.
-
D.
authorOfWorkAppearingIn
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
-
E.
authors
chosen
Indicates that one entity is the creator or writer of another entity, such as a document, work, or piece of content.
- 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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 3, 2026, 4:05 p.m.