Triple
T22379625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scoob! |
E553235
|
entity |
| Predicate | intendedTheatricalRelease |
P122193
|
FINISHED |
| Object | 2020-05-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: 2020-05-15 | Statement: [Scoob!, intendedTheatricalRelease, 2020-05-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedTheatricalRelease Context triple: [Scoob!, intendedTheatricalRelease, 2020-05-15]
-
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.
releaseDate_Theatrical
Indicates the date on which a work was first made publicly available in theaters.
-
C.
laterTheatricalReleaseWith
Indicates that one work had its theatrical release occur later than the theatrical release of another work.
-
D.
intendedTheater
Indicates the theater or venue that an event, performance, or screening is planned or meant to take place in.
-
E.
limitedTheatricalReleaseDate
Indicates the date on which a film first received a limited theatrical release, typically in a restricted number of cinemas or regions.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582afe6c819093940f9d817c64a8 |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.