Triple
T33191981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ethicon |
E849633
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Johnson & Johnson subsidiary |
C58690
|
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: Johnson & Johnson subsidiary Context triple: [Ethicon, instanceOf, Johnson & Johnson subsidiary]
-
A.
Berkshire Hathaway subsidiary
A Berkshire Hathaway subsidiary is a company in which Berkshire Hathaway holds a controlling ownership stake, operating independently while contributing to the conglomerate’s overall financial performance and strategic objectives.
-
B.
Fujitsu subsidiary
A Fujitsu subsidiary is a company that is owned or controlled by Fujitsu Limited and operates as part of its broader corporate group, often focusing on specific markets, technologies, or services.
-
C.
Johnson & Johnson facility
A Johnson & Johnson facility is a physical site where the company conducts its operations, such as research, manufacturing, packaging, or distribution of healthcare and consumer products, under regulated quality and safety standards.
-
D.
Samsung Group subsidiary
A Samsung Group subsidiary is a company that is owned or controlled by the Samsung conglomerate and operates in one of its diverse business sectors under the broader Samsung corporate umbrella.
-
E.
Vinci Group subsidiary
A Vinci Group subsidiary is a company that is majority-owned or controlled by Vinci Group and operates under its strategic, financial, and governance framework while conducting specific business activities within the group’s overall portfolio.
- F. None of above. chosen
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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:29 a.m.