Triple
T35548893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxygen (2021 film) |
E1027296
|
entity |
| Predicate | platformExclusiveAtRelease |
P89648
|
FINISHED |
| Object | Netflix |
—
|
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: Netflix | Statement: [Oxygen (2021 film), platformExclusiveAtRelease, Netflix]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformExclusiveAtRelease Context triple: [Oxygen (2021 film), platformExclusiveAtRelease, Netflix]
-
A.
platformExclusiveTo
Indicates that something is available or restricted to a single specific platform and not offered on others.
-
B.
exclusiveAtLaunch
chosen
Indicates that an item was available only through a specific platform, channel, or partner during its initial launch period.
-
C.
carrierExclusiveVariant
Indicates that a variant is available only through a specific carrier and not through others.
-
D.
regionExclusiveAtLaunch
Indicates that something was initially available only within a specific geographic region at the time of its launch.
-
E.
occursOnPlatform
Indicates that an event, action, or process takes place or is carried out on a specified platform.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.