Triple
T11218378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Aspern Papers (opera) |
E265495
|
entity |
| Predicate | sourceWorkSetting |
P15236
|
FINISHED |
| Object | 19th-century Venice |
—
|
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: 19th-century Venice | Statement: [The Aspern Papers (opera), sourceWorkSetting, 19th-century Venice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceWorkSetting Context triple: [The Aspern Papers (opera), sourceWorkSetting, 19th-century Venice]
-
A.
workSetting
Indicates the environment, context, or conditions in which the work or activity is carried out.
-
B.
settingOfWork
chosen
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
C.
hasSourceWork
Indicates that something originates from, is derived from, or is based on a particular source work.
-
D.
settingOfWorks
Indicates that a place or environment serves as the primary setting where the events or narratives of one or more works take place.
-
E.
sourceWorkFirstPerformed
Indicates the original performance event or context in which a work was first publicly performed.
- 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.