Triple
T12315896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ball Corporation |
E293597
|
entity |
| Predicate | saleOfBallAerospaceAnnounced |
P51163
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Ball Corporation, saleOfBallAerospaceAnnounced, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saleOfBallAerospaceAnnounced Context triple: [Ball Corporation, saleOfBallAerospaceAnnounced, 2023]
-
A.
soldAerospaceAndDefenseUnitsTo
Indicates that one entity transferred ownership of its aerospace and defense business units to another entity through a sale transaction.
-
B.
saleAnnouncedIn
chosen
Indicates that the occurrence or details of a sale are publicly communicated or reported within a particular medium, document, or announcement.
-
C.
soldTechnologyTo
Indicates that one entity transferred ownership or rights to a technology to another entity in exchange for compensation.
-
D.
saleTo
Indicates a transaction in which one party sells goods, services, or assets to another party.
-
E.
soldWellIn
Indicates that something achieved strong sales performance within a particular market, region, or time period.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.