Triple
T9250031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infineon Technologies |
E222297
|
entity |
| Predicate | acquisitionOfCypressSemiconductor |
P16131
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Infineon Technologies, acquisitionOfCypressSemiconductor, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionOfCypressSemiconductor Context triple: [Infineon Technologies, acquisitionOfCypressSemiconductor, 2020]
-
A.
acquisitionLed
Indicates that one entity’s acquisition of another directly caused or guided a subsequent outcome, change, or event.
-
B.
acquiredCompany
chosen
Indicates that one entity has purchased and taken ownership or control of another company.
-
C.
acquisitionResultedIn
Indicates that an acquisition event led to a particular outcome, state, or consequence for the involved entities.
-
D.
acquisitionType
Indicates the specific kind or category of acquisition relationship that exists between entities (such as a company buying another company, assets, or a controlling stake).
-
E.
acquiredWith
Indicates that one entity was obtained, purchased, or gained together with or by means of another entity.
- 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd05f7e9848190939f9199d0c1a572 |
completed | April 1, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4e79e48190b3200247f4624867 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:31 p.m.