Triple
T36606340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ways of Seeing |
E903052
|
entity |
| Predicate | publicationYearOfCompanionBook |
P193436
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Ways of Seeing, publicationYearOfCompanionBook, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationYearOfCompanionBook Context triple: [Ways of Seeing, publicationYearOfCompanionBook, 1972]
-
A.
companionVolumePublicationDate
chosen
Indicates the date on which a related companion volume was published.
-
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.
publisherOfCompanionBook
Indicates that an entity serves as the publisher responsible for producing and releasing a specific companion book.
-
D.
companionBookCoAuthor
Indicates that an entity is a co-author of a companion book associated with another work or subject.
-
E.
expandedBookPublicationYear
Indicates the year in which an expanded or revised edition of a book was published.
- 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_69f76e66b7b88190848f7a3e1188915f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
Created at: May 3, 2026, 4:11 p.m.