Triple
T28126911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yue opera |
E710952
|
entity |
| Predicate | notableTroupe |
P33774
|
FINISHED |
| Object | Shanghai Yue Opera Company |
—
|
NE NERFINISHED |
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: Shanghai Yue Opera Company | Statement: [Yue opera, notableTroupe, Shanghai Yue Opera Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTroupe Context triple: [Yue opera, notableTroupe, Shanghai Yue Opera Company]
-
A.
notableEnsemble
chosen
Indicates that an entity is a prominent or significant member of a particular group, band, or ensemble.
-
B.
notableTheatreCompanyAssociation
Indicates a significant or prominent association between an entity and a theatre company, such as major collaboration, membership, or recognized affiliation.
-
C.
featuresTroupe
Indicates that something includes or presents a particular troupe as part of its content or composition.
-
D.
notableArtistGroup
Indicates that an artist is a member of, or significantly associated with, a particular artist group or collective.
-
E.
performingCompany
Indicates the company that carries out or executes a given performance, production, or event.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
Created at: April 27, 2026, 9:20 p.m.