Triple
T5067312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athenahealth |
E114174
|
entity |
| Predicate | delistingDate |
P51857
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Athenahealth, delistingDate, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: delistingDate Context triple: [Athenahealth, delistingDate, 2019]
-
A.
delisted
chosen
Indicates that an entity has been removed from an official list, registry, or exchange where it was previously included.
-
B.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
-
C.
divestitureDate
Indicates the date on which an entity formally disposes of, sells, or otherwise relinquishes ownership or control of an asset, business unit, or investment.
-
D.
discontinuationAnnouncementDate
Indicates the date on which an official announcement is made that something (such as a product, service, or feature) will be discontinued.
-
E.
deJureRemovalDate
Indicates the official, legally recognized date on which an entity is formally removed from a position, status, or record.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd749bf69c819093e75dce56f1c0ab |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.