Triple
T34632849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The High Note |
E889333
|
entity |
| Predicate | originallyScheduledForTheatricalRelease |
P122193
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The High Note, originallyScheduledForTheatricalRelease, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyScheduledForTheatricalRelease Context triple: [The High Note, originallyScheduledForTheatricalRelease, true]
-
A.
originallyPlannedTheatricalRelease
chosen
Indicates the date or venue that was first intended for a work’s theatrical release before any later changes or rescheduling.
-
B.
originallyScheduledReleaseDate
Indicates the date on which something was first planned or intended to be released, before any later changes or rescheduling.
-
C.
releaseDate_Theatrical
Indicates the date on which a work was first made publicly available in theaters.
-
D.
limitedTheatricalReleaseDate
Indicates the date on which a film first received a limited theatrical release, typically in a restricted number of cinemas or regions.
-
E.
theatricalReleaseDateUS
Indicates the calendar date on which a work was first released theatrically in the United States.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2:04 a.m.