Triple
T32953831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cigna Corporation |
E843037
|
entity |
| Predicate | hasAcquired |
P88341
|
FINISHED |
| Object | Express Scripts |
—
|
NE NERFINISHED |
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: Express Scripts | Statement: [Cigna Corporation, hasAcquired, Express Scripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAcquired Context triple: [Cigna Corporation, hasAcquired, Express Scripts]
-
A.
hasAcquisition
chosen
Indicates that one entity has acquired ownership or control of another entity, typically through a purchase or merger transaction.
-
B.
acquiredWith
Indicates that one entity was obtained, purchased, or gained together with or by means of another entity.
-
C.
acquiredStatusOf
Indicates that one entity has obtained, taken over, or assumed the status or condition previously held by another entity.
-
D.
hasAcquisitionType
Indicates the specific kind or category of acquisition relationship that exists between one entity acquiring another.
-
E.
acquiredFor
Indicates that one entity obtained or purchased another entity specifically for the benefit, use, or purpose of a third 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_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 1, 2026, 1:21 a.m.