Triple
T26384525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amneris |
E663238
|
entity |
| Predicate | operaCatalogue |
P164665
|
FINISHED |
| Object | Verdi’s middle-late period |
—
|
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: Verdi’s middle-late period | Statement: [Amneris, operaCatalogue, Verdi’s middle-late period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaCatalogue Context triple: [Amneris, operaCatalogue, Verdi’s middle-late period]
-
A.
cataloguedWithOpera
chosen
Indicates that an item is recorded or documented in association with a specific opera work or opera-related cataloging system.
-
B.
operaAct
Indicates that an entity performs in or takes part in an act (segment) of an opera performance.
-
C.
inOperaRepertoire
Indicates that a musical work is included as part of the standard or active repertoire performed in opera productions.
-
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.
operaGenre
Indicates that an opera belongs to or is categorized under a particular musical or dramatic genre.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 26, 2026, 11:21 p.m.