Triple
T32060895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elemental |
E818742
|
entity |
| Predicate | disneyPlusRelease |
P38680
|
FINISHED |
| Object | 2023-09-13 |
—
|
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-09-13 | Statement: [Elemental, disneyPlusRelease, 2023-09-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disneyPlusRelease Context triple: [Elemental, disneyPlusRelease, 2023-09-13]
-
A.
releaseDate_DisneyPlus
chosen
Indicates the date on which a work becomes available for viewing on the Disney+ streaming platform.
-
B.
disneyPlusOriginal
Indicates that a work is an original production created specifically for and first released on the Disney+ streaming platform.
-
C.
streamingReleaseDate
Indicates the date on which a work (such as a film, show, or album) becomes available to the public via a streaming platform.
-
D.
theatricalReleaseWith
Indicates that two or more entities share the same theatrical release context, such as being released together or as part of the same theatrical event or distribution.
-
E.
theatricalReleaseIn
Indicates that a film or performance was released or shown theatrically in a specified location or market.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f5356c8190848a6ecf234db9da |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:21 a.m.