Triple
T10189089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Waverly Gallery |
E237984
|
entity |
| Predicate | broadwayPreviewStart |
P32921
|
FINISHED |
| Object | 2018-09-25 |
—
|
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: 2018-09-25 | Statement: [The Waverly Gallery, broadwayPreviewStart, 2018-09-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadwayPreviewStart Context triple: [The Waverly Gallery, broadwayPreviewStart, 2018-09-25]
-
A.
broadwayPreviewsBegin
chosen
Indicates the date on which a Broadway production begins its preview performances before the official opening.
-
B.
totalBroadwayPreviews
Indicates the total number of preview performances a Broadway production has had before its official opening.
-
C.
BroadwayRunStart
Indicates the date or point in time when a production’s run on Broadway begins.
-
D.
premiereOnBroadway
Indicates that a theatrical production has its first official public performance on Broadway.
-
E.
hasBroadwayOpeningContext
Indicates that an entity is associated with contextual details specifically about its Broadway opening (such as time, place, or circumstances of the premiere).
- 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_69ca84de1b208190bf17bb305b002605 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded7c3278819093312665b54d888c |
completed | April 2, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8477648190bc55c56aeec507d3 |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.