Triple
T7387844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altera Corporation |
E170425
|
entity |
| Predicate | delistedReason |
P30803
|
FINISHED |
| Object | acquisition by Intel Corporation |
—
|
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: acquisition by Intel Corporation | Statement: [Altera Corporation, delistedReason, acquisition by Intel Corporation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delistedReason Context triple: [Altera Corporation, delistedReason, acquisition by Intel Corporation]
-
A.
delisted
Indicates that an entity has been removed from an official list, registry, or exchange where it was previously included.
-
B.
reasonForDelisting
chosen
Indicates the specific cause or justification for which an item, entity, or record has been removed from a list or registry.
-
C.
decommissionedReason
Indicates the reason or cause for which an entity, typically an asset or system, was taken out of service or formally retired.
-
D.
inactivationReason
Indicates the reason or cause for which an entity, status, or process has been deactivated or made inactive.
-
E.
reasonForDisbandment
Indicates the cause or circumstance that led to a group, organization, or entity being dissolved or disbanded.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1f3f5f48190aabe69ba79cbcb93 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.