Triple
T32183063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XLNX |
E822034
|
entity |
| Predicate | associatedWithCorporateAction |
—
|
GENERATED |
| Object | merger |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCorporateAction Context triple: [XLNX, associatedWithCorporateAction, merger]
-
A.
associatedCompanyAction
Indicates that an action is performed by, on behalf of, or in direct connection with a particular company.
-
B.
associatedWithAction
chosen
Indicates a general relationship where an entity is linked or connected to a particular action, without specifying the nature or direction of that involvement.
-
C.
associatedWithCorporateEvent
Indicates that an entity has a connection or involvement with a specific corporate event.
-
D.
corporateActionsProcessedThrough
Indicates that corporate actions are executed, handled, or routed via a specified intermediary, system, or process.
-
E.
associatedWithRelationship
Indicates a general connection or involvement between entities through some form of relationship, without specifying its exact nature.
- F. None of above.
Provenance (1 batch)
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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:34 a.m.