Triple
T11218360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Aspern Papers (opera) |
E265495
|
entity |
| Predicate | sourceWorkPublicationForm |
P14177
|
FINISHED |
| Object | serialized fiction |
—
|
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: serialized fiction | Statement: [The Aspern Papers (opera), sourceWorkPublicationForm, serialized fiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceWorkPublicationForm Context triple: [The Aspern Papers (opera), sourceWorkPublicationForm, serialized fiction]
-
A.
publicationOfWork
Indicates that a particular work has been formally made public, typically through printing, distribution, or release by a publisher or similar entity.
-
B.
initialPublicationForm
chosen
Indicates the original format or medium in which a work was first published.
-
C.
workPublishedBy
Indicates that a work (such as a book, article, or other creation) has been issued or made publicly available by a particular publisher or publishing entity.
-
D.
publishingForm
Indicates the medium or format in which something is published or made publicly available.
-
E.
publicationAbout
Indicates that a publication has content whose subject or focus is the referenced entity.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ea19e8819095d5d02c1f145534 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.