Triple
T22987979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMO |
E571965
|
entity |
| Predicate | hasCostStructure |
P17476
|
FINISHED |
| Object | fixed monthly premium |
—
|
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: fixed monthly premium | Statement: [HMO, hasCostStructure, fixed monthly premium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCostStructure Context triple: [HMO, hasCostStructure, fixed monthly premium]
-
A.
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.
-
B.
costModel
chosen
Indicates the pricing or cost-structure relationship applied to an entity, defining how its costs are calculated or charged.
-
C.
economicCost
Indicates the financial burden, expense, or resource expenditure associated with an action, event, or relationship between entities.
-
D.
costsProvision
Indicates that providing a particular good, service, or resource requires incurring a specified cost.
-
E.
usesBillingModel
Indicates that one entity applies or operates under a particular billing model for charging or pricing purposes.
- 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829b4ea88190bc1a01183df7a1bb |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:49 p.m.