Triple
T24202059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | opera seria |
E600006
|
entity |
| Predicate | hasTheatricalConvention |
P155161
|
FINISHED |
| Object | exit aria convention |
—
|
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: exit aria convention | Statement: [opera seria, hasTheatricalConvention, exit aria convention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTheatricalConvention Context triple: [opera seria, hasTheatricalConvention, exit aria convention]
-
A.
hasTheatricalStyle
Indicates that one entity possesses, exhibits, or is characterized by a particular theatrical style associated with another entity.
-
B.
hasTheatricalForm
Indicates that something is associated with or presented in a particular theatrical form or style.
-
C.
hasTheatricalFilm
Indicates that an entity has an associated theatrical film adaptation, version, or release.
-
D.
hasTheatricalStaging
Indicates that something (such as a work or event) is presented or realized through a theatrical staging or performance.
-
E.
theatricalReleaseType
Indicates the manner or category of a work’s release in theaters, such as wide, limited, or special event distribution.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca1f3b481908c14052a8435fd21 |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:36 p.m.