Triple
T13833309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Shut Up in My Bones (opera) |
E332459
|
entity |
| Predicate | metOperaPremiereDate |
P29792
|
FINISHED |
| Object | 2021-09-27 |
—
|
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: 2021-09-27 | Statement: [Fire Shut Up in My Bones (opera), metOperaPremiereDate, 2021-09-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metOperaPremiereDate Context triple: [Fire Shut Up in My Bones (opera), metOperaPremiereDate, 2021-09-27]
-
A.
operaAdaptationPremiereYear
Indicates the year in which an opera adaptation of a work was first premiered.
-
B.
dateOfMetOperaDebut
chosen
Indicates the specific date on which an individual or group first performed at the Metropolitan Opera.
-
C.
operaPremiereContext
Indicates the circumstances or setting (such as time, place, or event) in which an opera had its premiere performance.
-
D.
associatedOpera
Indicates that there is a relationship linking an entity to an opera with which it is connected or related (e.g., as subject, inspiration, or context).
-
E.
madeMetropolitanOperaDebut
Indicates that an individual gave their first performance at the Metropolitan Opera.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de029a34bc8190ae892ef7b09fc9e9 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.