Triple
T12243294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act III (Turandot) |
E291786
|
entity |
| Predicate | premiereWorkPremiereDate |
P36066
|
FINISHED |
| Object | 25 April 1926 |
—
|
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: 25 April 1926 | Statement: [Act III (Turandot), premiereWorkPremiereDate, 25 April 1926]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiereWorkPremiereDate Context triple: [Act III (Turandot), premiereWorkPremiereDate, 25 April 1926]
-
A.
premiereOnPlatform
Indicates that a creative work has its first public release or debut on a specific distribution platform.
-
B.
revisedPremiereDate
Indicates that the originally scheduled premiere date of something has been changed to a new date.
-
C.
originalPlayPremiereYear
Indicates the calendar year in which the original production of a play was first premiered.
-
D.
festivalPremiereDate
Indicates the date on which a work (such as a film) first premieres at a festival.
-
E.
premieredOn
chosen
Indicates that an event, work, or production had its first public showing or debut on a specified date or at a specified time.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.