Triple
T38310168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Array Technology Inc. |
E1033660
|
entity |
| Predicate | acquisitionTargetAs |
P50794
|
FINISHED |
| Object | ATI Technologies Inc. |
—
|
NE NERFINISHED |
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: ATI Technologies Inc. | Statement: [Array Technology Inc., acquisitionTargetAs, ATI Technologies Inc.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionTargetAs Context triple: [Array Technology Inc., acquisitionTargetAs, ATI Technologies Inc.]
-
A.
acquisitionTarget
chosen
Indicates that one entity is the intended or actual company or asset being acquired by another in a merger or acquisition transaction.
-
B.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third entity.
-
C.
usesTargetsFrom
Indicates that one entity selects or operates on targets that are defined, provided, or referenced by another entity.
-
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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.