Triple
T10269523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Global Services |
E240797
|
entity |
| Predicate | customerPerception |
P5170
|
FINISHED |
| Object | exclusive status |
—
|
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: exclusive status | Statement: [United Global Services, customerPerception, exclusive status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customerPerception Context triple: [United Global Services, customerPerception, exclusive status]
-
A.
customerFocus
Indicates that one entity prioritizes understanding and meeting the needs, preferences, or satisfaction of another entity (typically a customer or client).
-
B.
marketReception
chosen
Indicates how a product, service, or work is received, evaluated, and responded to by the market or audience after its introduction.
-
C.
customerValue
Indicates the degree of benefit, importance, or worth that a customer represents to a business or organization.
-
D.
influencedPerceptionOf
Indicates that one entity has affected, shaped, or altered how another entity is perceived or understood.
-
E.
feedbackType
Indicates the specific category or nature of feedback associated with an action, event, or interaction.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2872830819080fdfa816167d04c |
completed | April 7, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69d4d1ef6e6c81908a8ee52e4d28127b |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:35 a.m.