Triple
T4089457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accountable Care Organizations |
E87668
|
entity |
| Predicate | usesPaymentModel |
P21228
|
FINISHED |
| Object | shared savings |
—
|
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: shared savings | Statement: [Accountable Care Organizations, usesPaymentModel, shared savings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPaymentModel Context triple: [Accountable Care Organizations, usesPaymentModel, shared savings]
-
A.
hasPaymentModel
chosen
Indicates that an entity uses, is associated with, or operates under a particular payment model or pricing scheme.
-
B.
hasPaymentOption
Indicates that an entity supports or offers a particular method or option for making payments.
-
C.
requiresPaymentOf
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
D.
hasAdvancePaymentOption
Indicates that an entity offers the possibility to pay, in full or in part, before the corresponding goods or services are delivered or consumed.
-
E.
usesBusinessModel
Indicates that one entity operates according to, or applies in practice, the business model defined or provided 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefca9e9088190a97cb2ccb5d622f0 |
completed | March 9, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.