Triple
T37588977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porgy |
E935203
|
entity |
| Predicate | firstOperaticAppearance |
P183948
|
FINISHED |
| Object | Porgy and Bess (1935) |
E55180
|
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: Porgy and Bess (1935) | Statement: [Porgy, firstOperaticAppearance, Porgy and Bess (1935)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOperaticAppearance Context triple: [Porgy, firstOperaticAppearance, Porgy and Bess (1935)]
-
A.
firstPerformanceInOpera
Indicates that an entity’s first-ever performance occurred in the context of an opera production.
-
B.
firstPerformanceOpera
Indicates the relationship in which an opera work is presented in its first-ever performance.
-
C.
madeOperaticDebut
Indicates that an entity performed in its first-ever opera production or role.
-
D.
madeOperaticDebutAt
chosen
Indicates the event, venue, or production at which a person first performed in an opera professionally.
-
E.
firstPerformanceOperaTitle
Indicates the title of the opera in which a given performance was the first performance.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40afdb36c88190b0d5ee0d61ac6459 |
completed | June 28, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.