Triple
T22041474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medicare beneficiaries |
E544645
|
entity |
| Predicate | mayHaveSupplementalCoverage |
P20051
|
FINISHED |
| Object | Medigap policy |
—
|
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: Medigap policy | Statement: [Medicare beneficiaries, mayHaveSupplementalCoverage, Medigap policy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHaveSupplementalCoverage Context triple: [Medicare beneficiaries, mayHaveSupplementalCoverage, Medigap policy]
-
A.
mayCover
Indicates that one entity is permitted or able to extend over, include, or provide coverage for another entity, either partially or fully.
-
B.
mayProvideEligibilityFor
Indicates that one entity can serve as a basis or qualifying factor that makes another entity eligible for something (such as a benefit, status, or action).
-
C.
hasDualEligibility
Indicates that an entity simultaneously qualifies for and is recognized under two distinct eligibility categories or programs.
-
D.
hasSupplement
chosen
Indicates that one entity provides or is associated with an additional supporting or enhancing item, resource, or component for another entity.
-
E.
medicalCoverageAfter
Indicates that one entity’s medical insurance coverage begins or applies after the time, event, or coverage period associated with 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12829c1c081909edc7544242c9c7a |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.