Triple
T37356347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hearst Magazines |
E927463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of Hearst Communications |
C169
|
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: division of Hearst Communications Context triple: [Hearst Magazines, instanceOf, division of Hearst Communications]
-
A.
division of the Associated Press
A division of the Associated Press is an organizational unit within the AP that focuses on a specific function, region, or media service, such as news gathering, multimedia production, or regional reporting.
-
B.
division of Publicis Groupe
A division of Publicis Groupe is an organizational unit within the global communications and marketing holding company that focuses on a specific set of services, markets, or capabilities while operating under the broader Publicis corporate structure.
-
C.
division of CBS
A division of CBS is a major organizational unit within the Columbia Broadcasting System responsible for managing a specific set of media operations, content areas, or business functions under the broader CBS corporate structure.
-
D.
former division of Guardian Media Group
A former division of Guardian Media Group is an organizational unit that once operated under the Guardian Media Group umbrella, managing specific media-related activities or assets before being restructured, sold, or dissolved.
-
E.
publishing division
chosen
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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.