Triple
T14993942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medicare for All |
E373907
|
entity |
| Predicate | coveragePopulation |
P2750
|
FINISHED |
| Object | all U.S. residents |
—
|
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: all U.S. residents | Statement: [Medicare for All, coveragePopulation, all U.S. residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveragePopulation Context triple: [Medicare for All, coveragePopulation, all U.S. residents]
-
A.
intendedCoveragePopulationShare
Indicates the proportion of a total population that a product, service, or intervention is intended or planned to cover.
-
B.
supportedPopulation
Indicates that one entity provides assistance, resources, or services to sustain or benefit a specified group of people.
-
C.
populationIncludes
chosen
Indicates that a population contains or encompasses the specified individual(s) or subgroup(s) as members or elements.
-
D.
hasServiceAreaPopulation
Indicates that an entity has a service area characterized by a specific population size or count.
-
E.
relativePopulation
Indicates the comparative size of one population relative to another, typically expressing how large, small, or proportionate it is.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded716ebb481908224d2d4f7561b03 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:53 a.m.