Triple
T14993940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medicare for All |
E373907
|
entity |
| Predicate | proposesSystemType |
P55526
|
FINISHED |
| Object | single-payer healthcare system |
—
|
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: single-payer healthcare system | Statement: [Medicare for All, proposesSystemType, single-payer healthcare system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesSystemType Context triple: [Medicare for All, proposesSystemType, single-payer healthcare system]
-
A.
proposesSystem
chosen
Indicates that one entity formally suggests or puts forward a particular system for consideration, adoption, or implementation by another entity.
-
B.
definesSystemAs
Indicates that one entity explicitly specifies or establishes another entity as the system to be used, referenced, or treated as authoritative.
-
C.
rackSystemType
Indicates the specific configuration or category of rack system associated with an entity.
-
D.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
E.
supportedSystem
Indicates that one entity provides compatibility, functionality, or operational support for another system.
- 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.