Triple
T36606336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ways of Seeing |
E903052
|
entity |
| Predicate | companionBookCoAuthor |
P194396
|
FINISHED |
| Object | Sven Blomberg |
—
|
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: Sven Blomberg | Statement: [Ways of Seeing, companionBookCoAuthor, Sven Blomberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companionBookCoAuthor Context triple: [Ways of Seeing, companionBookCoAuthor, Sven Blomberg]
-
A.
publisherOfCompanionBook
Indicates that an entity serves as the publisher responsible for producing and releasing a specific companion book.
-
B.
hasCompanionBook
Indicates that one entity (typically a primary work) is associated with another entity that serves as its companion book, providing supplementary or related content.
-
C.
authorOfCompanionWork
Indicates that one entity is the creator or writer of another entity that serves as a companion or supplementary work to a primary work.
-
D.
coAuthorAlsoWrote
Indicates that a person who is a co-author of one work also wrote another work, linking shared authorship across multiple creations.
-
E.
companionVolumePublicationDate
Indicates the date on which a related companion volume was published.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: May 3, 2026, 4:11 p.m.