Triple
T3831941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MG ZS |
E91031
|
entity |
| Predicate | salesStrength |
P17973
|
FINISHED |
| Object | strong sales in UK private buyer segment |
—
|
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: strong sales in UK private buyer segment | Statement: [MG ZS, salesStrength, strong sales in UK private buyer segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: salesStrength Context triple: [MG ZS, salesStrength, strong sales in UK private buyer segment]
-
A.
salesPerformance
chosen
Indicates how effectively an entity achieves its sales objectives, typically measured by revenue, volume, or growth over a given period.
-
B.
salesMilestone
Indicates that a specific sales target or threshold has been reached or surpassed.
-
C.
salesUS
Indicates a relationship where sales activity, revenue, or transactions are specifically associated with the United States.
-
D.
salesRole
Indicates that an entity holds a position or function related to selling products or services within a business context.
-
E.
strengths
Indicates that one entity possesses notable abilities, advantages, or positive qualities in relation to another entity or context.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8787bc8190819a7af975b609df |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74c2e04819094b94b3c0bac1806 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.