Triple
T12199058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Un ballo in maschera |
E290664
|
entity |
| Predicate | operaNumberInVerdiOeuvre |
P104277
|
FINISHED |
| Object | 23 |
—
|
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: 23 | Statement: [Un ballo in maschera, operaNumberInVerdiOeuvre, 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaNumberInVerdiOeuvre Context triple: [Un ballo in maschera, operaNumberInVerdiOeuvre, 23]
-
A.
operaNumberInMozartsOutput
Indicates the ordinal position or catalog number assigned to an opera within the complete body of Mozart’s operatic works.
-
B.
estimatedNumberOfOperas
Indicates the approximate count of operas associated with an entity, rather than an exact, verified number.
-
C.
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).
-
D.
inOperaRepertoire
Indicates that a musical work is included as part of the standard or active repertoire performed in opera productions.
-
E.
hasOpusNumber
Indicates that a musical work is associated with a specific opus number assigned to it, typically denoting its place in a composer’s catalog.
- 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_69d6ab65923081909acfc61b7a612233 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d938cd2edc8190b1971349dbc0dee0 |
completed | April 10, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69d91c38321c819080d500d0d64a04f6 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d938ca32908190bd56f563efcbe8a0 |
completed | April 10, 2026, 5:52 p.m. |
Created at: April 8, 2026, 9:50 p.m.