Triple
T7944357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadcom |
E184462
|
entity |
| Predicate | notableCustomerSegments |
P927
|
FINISHED |
| Object | hyperscale cloud providers |
—
|
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: hyperscale cloud providers | Statement: [Broadcom, notableCustomerSegments, hyperscale cloud providers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCustomerSegments Context triple: [Broadcom, notableCustomerSegments, hyperscale cloud providers]
-
A.
marketSegmentCoverage
Indicates the extent to which a product, service, or campaign reaches or serves the intended market segment(s).
-
B.
targetMarket
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
C.
brandSegment
Indicates the specific market segment or customer group that a brand is targeted toward or associated with.
-
D.
majorCustomer
chosen
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
E.
countrySegment
Indicates that something represents a specific geographic or administrative segment or portion within a country.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0e84448190a7e8e0749776a592 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.