Triple
T29248856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peek Performance |
E741504
|
entity |
| Predicate | companyFocus |
P6749
|
FINISHED |
| Object | Apple silicon performance |
—
|
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: Apple silicon performance | Statement: [Peek Performance, companyFocus, Apple silicon performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: companyFocus Context triple: [Peek Performance, companyFocus, Apple silicon performance]
-
A.
underlyingCompanyBusinessFocus
chosen
Indicates the primary industry, sector, or type of business activity that the underlying company is focused on.
-
B.
organizationFocus
Indicates the primary area of activity, mission, or specialization that an organization is oriented toward or concentrated on.
-
C.
acquiredCompanyFocus
Indicates that a company’s primary business focus or specialization changed as a result of acquiring another company.
-
D.
brandFocus
Indicates that a brand primarily concentrates its efforts, messaging, or resources on a particular target, theme, or market segment.
-
E.
employerFocus
Indicates that an employer directs particular attention, resources, or priority toward a specific subject, group, or area.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 28, 2026, 12:33 p.m.