Triple
T32953833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cigna Corporation |
E843037
|
entity |
| Predicate | acquisitionOfExpressScriptsCompleted |
P23562
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Cigna Corporation, acquisitionOfExpressScriptsCompleted, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionOfExpressScriptsCompleted Context triple: [Cigna Corporation, acquisitionOfExpressScriptsCompleted, 2018]
-
A.
acquisitionResultedIn
Indicates that an acquisition event led to a particular outcome, state, or consequence for the involved entities.
-
B.
acquisitionStatus
chosen
Indicates the current state or outcome of an acquisition process between entities (e.g., pending, completed, failed, or canceled).
-
C.
postAcquisitionStatus
Indicates the condition or state of an entity after it has been acquired by another party.
-
D.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
-
E.
acquiredStatusOf
Indicates that one entity has obtained, taken over, or assumed the status or condition previously held by another entity.
- 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_69f3494a31f481909057136e49b4fe60 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:21 a.m.