Triple
T34981301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dead City |
E1008821
|
entity |
| Predicate | librettistPseudonymOf |
P179136
|
FINISHED |
| Object | Julius Korngold |
—
|
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: Julius Korngold | Statement: [The Dead City, librettistPseudonymOf, Julius Korngold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: librettistPseudonymOf Context triple: [The Dead City, librettistPseudonymOf, Julius Korngold]
-
A.
librettistRealName
chosen
Indicates that the real, legal name of a librettist is being specified or linked to their professional or credited identity.
-
B.
librettistOfOpera
Indicates that one entity is the librettist who wrote the text (libretto) for the specified opera.
-
C.
librettistNationality
Indicates the relationship between a librettist and the country or nationality with which they are associated.
-
D.
librettistOfWorkAppearingIn
Indicates that a person is the librettist responsible for the text of a work that appears within a larger composite work or collection.
-
E.
librettistOfParentWork
Indicates that one entity is the librettist who wrote the text (libretto) for the parent work associated with another 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.