Triple
T9131871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rahway Road Productions |
E219104
|
entity |
| Predicate | distributionPartners |
P61791
|
FINISHED |
| Object | major streaming platforms |
—
|
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: major streaming platforms | Statement: [Rahway Road Productions, distributionPartners, major streaming platforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributionPartners Context triple: [Rahway Road Productions, distributionPartners, major streaming platforms]
-
A.
hasDistributionPartners
chosen
Indicates that an entity collaborates with other entities to distribute its products or services.
-
B.
distributionToPartners
Indicates the allocation or transfer of resources, benefits, or proceeds from a source entity to its partner entities.
-
C.
segmentPartner
Indicates a partnership relationship between entities within a specific segment, context, or category.
-
D.
exportPartners
Indicates a relationship where one entity collaborates with or serves as a partner to another in exporting goods or services across borders.
-
E.
distributorType
Indicates the specific category or role of a distributor in relation to the distribution of a product or service.
- 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_69ca83debfc0819095800583e97ab10f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8db7d808190bd22b0e5a6f9c285 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:18 p.m.