Triple
T25387479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yum-Yum |
E631563
|
entity |
| Predicate | firstPerformanceWorkPremiereYear |
P143079
|
FINISHED |
| Object | 1885 |
—
|
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: 1885 | Statement: [Yum-Yum, firstPerformanceWorkPremiereYear, 1885]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPerformanceWorkPremiereYear Context triple: [Yum-Yum, firstPerformanceWorkPremiereYear, 1885]
-
A.
firstPerformanceOfWorkYear
Indicates that the referenced performance is the first time a particular work was performed in a given calendar year.
-
B.
firstPerformanceAt
Indicates the location or event at which an entity (such as a work or performance) was first performed.
-
C.
firstPerformanceBy
Indicates that the referenced performance is the earliest or debut performance carried out by the specified entity.
-
D.
premieredInWorkPremiereYear
chosen
Indicates the year in which a work (such as a performance, film, or composition) had its first public premiere.
-
E.
dateOfFirstPerformance
Indicates the date on which a work, such as a play or musical composition, was first publicly performed.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 21, 2026, 1:47 p.m.