Triple
T22245504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan K |
E549829
|
entity |
| Predicate | typeOfCostSharing |
P116450
|
FINISHED |
| Object | coinsurance |
—
|
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: coinsurance | Statement: [Plan K, typeOfCostSharing, coinsurance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCostSharing Context triple: [Plan K, typeOfCostSharing, coinsurance]
-
A.
costSharing
chosen
Indicates how the financial burden of a cost is divided or shared among multiple parties.
-
B.
coversCosts
Indicates that one party assumes responsibility for paying or reimbursing the expenses incurred by another party.
-
C.
costToUser
Indicates the amount of cost or expense that is borne by, charged to, or incurred by the user.
-
D.
chargeType
Indicates the category or nature of a charge applied in a transaction or interaction between entities (e.g., fee type, billing classification, or legal charge type).
-
E.
hasCost
Indicates that one entity requires a specified amount of resources (such as money, time, or effort) to be obtained, used, or maintained by 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_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.