Triple
T37059628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I puritani |
E917286
|
entity |
| Predicate | originalPremiereCompany |
P12045
|
FINISHED |
| Object | Théâtre-Italien company |
E717574
|
NE 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: Théâtre-Italien company | Statement: [I puritani, originalPremiereCompany, Théâtre-Italien company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPremiereCompany Context triple: [I puritani, originalPremiereCompany, Théâtre-Italien company]
-
A.
premieredWithCompany
chosen
Indicates that a work or production had its first public performance or showing under the auspices of a specific company.
-
B.
firstProductionCompany
Indicates that the related entity is the primary or earliest production company associated with a work or project.
-
C.
productionCompanyOfOrigin
Indicates the company that originally produced or was primarily responsible for creating a given work or product.
-
D.
producerOfPremiere
Indicates that an entity served as the producer responsible for the premiere of a work or event.
-
E.
premiereEdition
Indicates that an entity is the first or original edition in which a work was initially released or premiered.
- F. None of above.
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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e8c53fd988190aaf6521e5984470b |
completed | June 26, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.