Triple
T23268962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hello, Dolly! (2017 Broadway revival) |
E588236
|
entity |
| Predicate | beganPreviewsOn |
P32921
|
FINISHED |
| Object | 2017-03-15 |
—
|
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: 2017-03-15 | Statement: [Hello, Dolly! (2017 Broadway revival), beganPreviewsOn, 2017-03-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganPreviewsOn Context triple: [Hello, Dolly! (2017 Broadway revival), beganPreviewsOn, 2017-03-15]
-
A.
previewStartDate
Indicates the date and time when a preview period for something begins.
-
B.
startedShowOn
Indicates that an entity initiated or began broadcasting or presenting a particular show on a specified platform, channel, or service.
-
C.
broadwayPreviewsBegin
chosen
Indicates the date on which a Broadway production begins its preview performances before the official opening.
-
D.
developmentBegan
Indicates that the process of creating or developing something was initiated at a particular time or under certain conditions.
-
E.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
- 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_69e25d148adc819088efbf42672604e9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957219188190b30bceffad1542da |
completed | April 29, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:44 p.m.