Triple
T37381218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papagena |
E928435
|
entity |
| Predicate | culturalOriginOfWork |
P56388
|
FINISHED |
| Object | Austrian |
—
|
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: Austrian | Statement: [Papagena, culturalOriginOfWork, Austrian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culturalOriginOfWork Context triple: [Papagena, culturalOriginOfWork, Austrian]
-
A.
culturalContextOfWork
Indicates the cultural setting, traditions, or background within which a work was created, interpreted, or is meaningfully situated.
-
B.
originatedInCulturalContext
Indicates that something began, developed, or was created within a particular cultural setting, tradition, or milieu.
-
C.
genreOfOriginWork
Indicates that a work is classified under a particular genre based on the genre of its original source work.
-
D.
culturalWorkCreatedThere
Indicates that a cultural work (such as a book, film, artwork, or performance) was created, produced, or originated at a particular place.
-
E.
cultureOfOrigin
chosen
Indicates the cultural background or tradition from which an entity originates or is derived.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:16 p.m.