Triple
T8472297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motorola, Inc. |
E200307
|
entity |
| Predicate | majorCustomerSegment |
P82393
|
FINISHED |
| Object | mobile phone consumers |
—
|
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: mobile phone consumers | Statement: [Motorola, Inc., majorCustomerSegment, mobile phone consumers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCustomerSegment Context triple: [Motorola, Inc., majorCustomerSegment, mobile phone consumers]
-
A.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
B.
majorSegmentOf
Indicates that one entity constitutes a principal or most significant part of another larger whole.
-
C.
commercialCustomer
Indicates a relationship where an entity purchases or uses goods or services from another entity for commercial or business purposes.
-
D.
brandSegment
Indicates the specific market segment or customer group that a brand is targeted toward or associated with.
-
E.
customerGroup
chosen
Indicates a relationship in which an entity belongs to, is classified under, or is associated with a particular group of customers.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f4fbf481909e4fd7c078b27477 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.