Triple

T26378011
Position Surface form Disambiguated ID Type / Status
Subject Altera Hardware Description Language E660949 entity
Predicate associatedWithCompanyEvent P46794 FINISHED
Object Intel acquisition of Altera in 2015 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: Intel acquisition of Altera in 2015 | Statement: [Altera Hardware Description Language, associatedWithCompanyEvent, Intel acquisition of Altera in 2015]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedWithCompanyEvent
Context triple: [Altera Hardware Description Language, associatedWithCompanyEvent, Intel acquisition of Altera in 2015]
  • A. associatedWithCorporateEvent chosen
    Indicates that an entity has a connection or involvement with a specific corporate event.
  • B. associatedWithEventHost
    Indicates that an entity has a relationship or connection with the host of a particular event.
  • C. associatedCompanyAction
    Indicates that an action is performed by, on behalf of, or in direct connection with a particular company.
  • D. associatedWithCompanyLogo
    Indicates a relationship where something is linked or connected to a specific company’s logo, such as by use, display, or representation.
  • E. relationshipToEvent
    Indicates the specific way an entity is connected or related to a particular event.
  • 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_69ee812a698881908d6a58265995fa39 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69ff1f3f94fc819095955299f50ab4ce completed May 9, 2026, 11:49 a.m.
PD Predicate disambiguation batch_69ff1ea47748819082f63d9b9d9c3e65 completed May 9, 2026, 11:46 a.m.
Created at: April 26, 2026, 11:02 p.m.