Triple
T28978482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blade (Marvel Cinematic Universe film) |
E734481
|
entity |
| Predicate | intendedReleaseFormat |
P32198
|
FINISHED |
| Object | theatrical release |
—
|
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: theatrical release | Statement: [Blade (Marvel Cinematic Universe film), intendedReleaseFormat, theatrical release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedReleaseFormat Context triple: [Blade (Marvel Cinematic Universe film), intendedReleaseFormat, theatrical release]
-
A.
subsequentReleaseFormat
Indicates that one media release is issued in a different format that chronologically follows an earlier release of the same content.
-
B.
typicalReleaseFormat
chosen
Indicates the usual or standard format in which something is released or published.
-
C.
intendedForReleaseIn
Indicates that something is planned or scheduled to be made available or launched within a specified context, such as a time, market, or platform.
-
D.
firstReleaseFormat
Indicates the original medium or format in which something (such as a work or product) was first released.
-
E.
targetRelease
Indicates the specific release or version that an item (such as a feature, fix, or component) is planned or designated to be delivered in.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 28, 2026, 9:10 a.m.