Triple
T20391146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C2 Pictures |
E498085
|
entity |
| Predicate | distributionVia |
P139939
|
FINISHED |
| Object | major Hollywood studios |
—
|
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 Hollywood studios | Statement: [C2 Pictures, distributionVia, major Hollywood studios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distributionVia Context triple: [C2 Pictures, distributionVia, major Hollywood studios]
-
A.
distributionBy
Indicates how something is allocated, arranged, or spread according to a specified criterion or grouping.
-
B.
distribution
Indicates the act or pattern of giving, delivering, or spreading something from one source to multiple recipients or locations.
-
C.
distributedAs
Indicates that something is allocated, delivered, or spread out according to a particular pattern, rule, or distribution scheme.
-
D.
distributionHub
Indicates a location or facility that serves as a central point for receiving, sorting, and redistributing goods or resources to multiple destinations.
-
E.
distributedWith
Indicates that one entity is supplied, packaged, or made available together with another entity as part of the same distribution.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6790f8d9c819093038f6bb6f47a92 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:28 a.m.