Triple
T22041479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medicare beneficiaries |
E544645
|
entity |
| Predicate | primaryEligibilityCriterion |
P7594
|
FINISHED |
| Object | age 65 or older |
—
|
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: age 65 or older | Statement: [Medicare beneficiaries, primaryEligibilityCriterion, age 65 or older]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryEligibilityCriterion Context triple: [Medicare beneficiaries, primaryEligibilityCriterion, age 65 or older]
-
A.
primaryCriterion
chosen
Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
-
B.
eligibilityCriteria
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible for something.
-
C.
eligibility
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
D.
customaryEligibility
Indicates that an entity qualifies for something based on established customs, norms, or usual practice rather than formal or exceptional criteria.
-
E.
primaryStatus
Indicates the main or most important status assigned to an entity among potentially multiple statuses.
- 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.