Triple
T32902327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act I Prelude |
E841644
|
entity |
| Predicate | parentWorkPremiereDate |
P192856
|
FINISHED |
| Object | 1868-06-21 |
—
|
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: 1868-06-21 | Statement: [Act I Prelude, parentWorkPremiereDate, 1868-06-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentWorkPremiereDate Context triple: [Act I Prelude, parentWorkPremiereDate, 1868-06-21]
-
A.
parentWorkPremiereCountry
Indicates the country where the premiere of the parent work (from which this work is derived) took place.
-
B.
premieredInWorkPremiereYear
Indicates the year in which a work (such as a performance, film, or composition) had its first public premiere.
-
C.
placeOfWorkPremiere
Indicates the location where a person’s work or performance was first publicly presented or debuted.
-
D.
regularPremiereDate
Indicates the calendar date on which something (such as a show, event, or series) begins its standard or ongoing run after any initial or special premieres.
-
E.
workCompletePremiereDate
Indicates the date on which the work’s premiere was fully completed or first made ready for public presentation.
- F. None of above. chosen
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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
| PDg | Predicate description generation | batch_69fd2cf29f808190856ab1d43a51d5c7 |
completed | May 8, 2026, 12:23 a.m. |
Created at: May 1, 2026, 1:19 a.m.