Triple
T31945147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuit d’ivresse et d’extase infinie |
E815629
|
entity |
| Predicate | operaPremiereOfWork |
P64201
|
FINISHED |
| Object | 1863 |
—
|
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: 1863 | Statement: [Nuit d’ivresse et d’extase infinie, operaPremiereOfWork, 1863]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaPremiereOfWork Context triple: [Nuit d’ivresse et d’extase infinie, operaPremiereOfWork, 1863]
-
A.
operaHouseOfPremiere
Indicates the opera house where a particular work was first premiered or originally performed.
-
B.
operaAdaptationPremiereYear
chosen
Indicates the year in which an opera adaptation of a work was first premiered.
-
C.
premieredWorkBy
Indicates that a creative work had its first public performance, showing, or presentation conducted by the specified entity.
-
D.
operaPremiereContext
Indicates the circumstances or setting (such as time, place, or event) in which an opera had its premiere performance.
-
E.
theatricalProductionPremiereYear
Indicates the year in which a theatrical production was first premiered or 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
Created at: May 1, 2026, 12:06 a.m.