Triple
T22245403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan F |
E549827
|
entity |
| Predicate | stillAvailableTo |
P85954
|
FINISHED |
| Object | people who were eligible for Medicare before January 1, 2020 |
—
|
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: people who were eligible for Medicare before January 1, 2020 | Statement: [Plan F, stillAvailableTo, people who were eligible for Medicare before January 1, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stillAvailableTo Context triple: [Plan F, stillAvailableTo, people who were eligible for Medicare before January 1, 2020]
-
A.
availableFor
Indicates that one entity can be used, accessed, or allocated for the benefit, purpose, or use of another entity.
-
B.
availableWith
Indicates that one entity can be obtained, accessed, or used in conjunction with another entity.
-
C.
initialAvailability
Indicates the starting level or state of availability of an entity before any changes or updates occur.
-
D.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
E.
availabilityEnd
chosen
Indicates the point in time or condition after which something is no longer available or offered.
- 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_69e11e41d9408190bd770cf282e22753 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f13217c9f88190aa2ce7d644b57739 |
completed | April 28, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:38 p.m.