Triple
T15799774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSM |
E383066
|
entity |
| Predicate | associatedCompanyProductType |
P94523
|
FINISHED |
| Object | integrated circuits |
—
|
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: integrated circuits | Statement: [NSM, associatedCompanyProductType, integrated circuits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanyProductType Context triple: [NSM, associatedCompanyProductType, integrated circuits]
-
A.
associatedCompanyMainProductLine
Indicates that a company’s primary or main line of products is linked or related to a specified product category or product line.
-
B.
relatedCompanyType
Indicates the type or nature of the relationship that one company has to another company.
-
C.
associatedCompanySpecialization
Indicates that a company is linked to a particular area of specialization or expertise.
-
D.
associatedCompanyGlobalScope
Indicates that there is a relationship linking an entity to a company at a global (worldwide) organizational scope.
-
E.
associatedCompanyBusinessSegment
chosen
Indicates that a company is linked to a specific business segment through its operations, products, or services.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4e135b08190b736e77bac5e2bff |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.