Triple
T35598756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM10 operational amplifier |
E1028707
|
entity |
| Predicate | originalCompanySubsequentlyAcquiredBy |
P22682
|
FINISHED |
| Object | Texas Instruments |
E369
|
NE 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: Texas Instruments | Statement: [LM10 operational amplifier, originalCompanySubsequentlyAcquiredBy, Texas Instruments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCompanySubsequentlyAcquiredBy Context triple: [LM10 operational amplifier, originalCompanySubsequentlyAcquiredBy, Texas Instruments]
-
A.
acquiredCompany
Indicates that one entity has purchased and taken ownership or control of another company.
-
B.
laterAcquiredBy
chosen
Indicates that one entity was acquired by another entity at a later point in time, after some prior state or ownership.
-
C.
parentCompanyAfterMerger
Indicates that one company is the resulting parent company of another following a merger.
-
D.
underlyingCompanyAcquisition
Indicates that one company is the target or subject of an acquisition by another company.
-
E.
associatedCompanyTradedAs
Indicates that a company is linked to the stock ticker, trading name, or market symbol under which it is publicly traded.
- F. None of above.
Provenance (4 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3868449a5c8190881b0b9bf182d299 |
completed | June 21, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.