Triple
T8107505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amor (Gluck) |
E189262
|
entity |
| Predicate | operaPremiereContext |
P80488
|
FINISHED |
| Object | Paris version of Orphée et Eurydice (1774) |
—
|
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: Paris version of Orphée et Eurydice (1774) | Statement: [Amor (Gluck), operaPremiereContext, Paris version of Orphée et Eurydice (1774)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaPremiereContext Context triple: [Amor (Gluck), operaPremiereContext, Paris version of Orphée et Eurydice (1774)]
-
A.
operaAdaptationPremiereYear
Indicates the year in which an opera adaptation of a work was first premiered.
-
B.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
C.
premiereOnBroadway
Indicates that a theatrical production has its first official public performance on Broadway.
-
D.
firstPerformanceOpera
Indicates the relationship in which an opera work is presented in its first-ever performance.
-
E.
conductorAtPremiere
Indicates that a person served as the conductor for the first public performance (premiere) of a specific work or event.
- F. None of above. chosen
Provenance (4 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42f89dd481908f1a25e4b16a8fc8 |
completed | March 31, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69cb04a2ed1c8190b73562321ad688bc |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:32 p.m.