Triple
T29051235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvel Comics adaptations |
E735264
|
entity |
| Predicate | hasNotableStreamingPartner |
P200044
|
FINISHED |
| Object | Disney+ |
—
|
NE NERFINISHED |
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: Disney+ | Statement: [Marvel Comics adaptations, hasNotableStreamingPartner, Disney+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableStreamingPartner Context triple: [Marvel Comics adaptations, hasNotableStreamingPartner, Disney+]
-
A.
hasOnscreenPartner
Indicates that one entity appears together with another as a partner within the same onscreen context or scene.
-
B.
hasNotableFranchisePartner
Indicates that an entity has a significant or prominent partner involved in a franchise relationship with it.
-
C.
exclusiveStreamingPartnerFromYear
Indicates that one entity has been the sole authorized streaming partner for another entity starting from a specified year.
-
D.
hasStreamingEligibility
Indicates that an entity is qualified or permitted to be made available via a streaming service or platform.
-
E.
hasOnlineStreamingSuccess
Indicates that an entity has achieved notable popularity, viewership, or impact through online streaming platforms.
- F. None of above. chosen
Provenance (4 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff6ef0d61c81909162d37c15a1a3c3 |
completed | May 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ff6c6a58e08190921317062cd9d489 |
completed | May 9, 2026, 5:18 p.m. |
| PDg | Predicate description generation | batch_69ff6eefa9c48190aac36916990f6db5 |
completed | May 9, 2026, 5:29 p.m. |
Created at: April 28, 2026, 10:08 a.m.