Triple
T32508082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huangmei opera |
E830854
|
entity |
| Predicate | famousWork |
P4
|
FINISHED |
| Object | The Heavenly Maid Scatters Blossoms |
—
|
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: The Heavenly Maid Scatters Blossoms | Statement: [Huangmei opera, famousWork, The Heavenly Maid Scatters Blossoms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousWork Context triple: [Huangmei opera, famousWork, The Heavenly Maid Scatters Blossoms]
-
A.
famousWorkInKey
Indicates that a notable or renowned work is composed or set in a particular musical key.
-
B.
notableWorkIn
Indicates that an entity is known for or associated with a significant work, contribution, or achievement in a particular field or context.
-
C.
isFamousWorkOf
Indicates that one entity is a well-known or widely recognized work created by another entity (typically an artist, author, or creator).
-
D.
notableWork
chosen
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
E.
notableWorkAs
Indicates a relationship where a particular work is recognized as a significant or distinguished creation associated with an entity.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c44d21648190ada905d52e251b1f |
completed | May 3, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.