Triple
T32183063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XLNX |
E822034
|
entity |
| Predicate | associatedWithCorporateAction |
P54902
|
FINISHED |
| Object | merger |
—
|
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: merger | Statement: [XLNX, associatedWithCorporateAction, merger]
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 (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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:34 a.m.