Triple
T8335844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warner Bros. Consumer Products |
E195783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | licensing division |
C3497
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: licensing division Context triple: [Warner Bros. Consumer Products, instanceOf, licensing division]
-
A.
division of the U.S. Copyright Office
A division of the U.S. Copyright Office is an organizational unit responsible for specific functions such as registration, recordation, policy analysis, public information, or administrative support within the Office’s overall mission to administer and interpret U.S. copyright law.
-
B.
standardized license
A standardized license is a pre-defined, widely accepted legal agreement that sets uniform terms and conditions for using, sharing, or distributing a product, service, or intellectual property.
-
C.
specialized division
chosen
A specialized division is a distinct organizational unit focused on a specific function, expertise, or market segment to improve efficiency and effectiveness within a larger entity.
-
D.
semiconductor company division
A semiconductor company division is an organizational unit within a semiconductor firm responsible for specific product lines, technologies, or market segments, managing everything from design and development to marketing and support for its assigned portfolio.
-
E.
publishing division
A publishing division is an organizational unit within a company responsible for acquiring, producing, marketing, and distributing content such as books, journals, or digital media.
- F. None of above.
Provenance (1 batch)
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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:57 p.m.