Triple
T37358863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Il mio tesoro |
E927525
|
entity |
| Predicate | numberInOpera |
P187988
|
FINISHED |
| Object | aria of Don Ottavio in Act II |
—
|
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: aria of Don Ottavio in Act II | Statement: [Il mio tesoro, numberInOpera, aria of Don Ottavio in Act II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInOpera Context triple: [Il mio tesoro, numberInOpera, aria of Don Ottavio in Act II]
-
A.
numberOfOperas
Indicates the total count of operas associated with a given entity (such as a person, organization, or catalog entry).
-
B.
movementNumberInOpera
chosen
Indicates the specific numbered position that a musical movement occupies within an opera.
-
C.
estimatedNumberOfOperas
Indicates the approximate count of operas associated with an entity, rather than an exact, verified number.
-
D.
operaNumberType
Indicates the type or classification assigned to an opera’s identifying number within a cataloging or numbering system.
-
E.
workNumberInOpera
Indicates the numerical position or catalog number assigned to a specific work within an 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.