Triple
T11762129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Once Upon a One More Time |
E279681
|
entity |
| Predicate | openedOnBroadwayDate |
P40638
|
FINISHED |
| Object | 2023-06-22 |
—
|
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: 2023-06-22 | Statement: [Once Upon a One More Time, openedOnBroadwayDate, 2023-06-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedOnBroadwayDate Context triple: [Once Upon a One More Time, openedOnBroadwayDate, 2023-06-22]
-
A.
originalBroadwayOpeningDate
chosen
Indicates the calendar date on which a production first opened on Broadway in its original run.
-
B.
offBroadwayOpeningDate
Indicates the date on which a production first opened in an Off-Broadway venue.
-
C.
offBroadwayPremiereYear
Indicates the year in which a work (such as a play or musical) first premiered in an Off-Broadway production.
-
D.
hasBroadwayOpeningContext
Indicates that an entity is associated with contextual details specifically about its Broadway opening (such as time, place, or circumstances of the premiere).
-
E.
firstBroadwayProductionYear
Indicates the calendar year in which an entity’s first production was staged on Broadway.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a52386708190b744746a2db37495 |
completed | April 10, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69d88a829fe481909cc5431de7d6058e |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.