Triple
T22245355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan C |
E549826
|
entity |
| Predicate | premiumPaidTo |
P41195
|
FINISHED |
| Object | private insurance companies |
—
|
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: private insurance companies | Statement: [Plan C, premiumPaidTo, private insurance companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiumPaidTo Context triple: [Plan C, premiumPaidTo, private insurance companies]
-
A.
premiumTierBackedBy
Indicates that a premium tier is supported, guaranteed, or underwritten by a specified backing entity or resource.
-
B.
paidTierIncludes
Indicates that a paid subscription tier encompasses or provides access to a specified feature, service, or benefit.
-
C.
paidTierName
Indicates the specific name or label of the paid subscription tier associated with an entity.
-
D.
paidFor
chosen
Indicates that one entity provided payment to cover the cost of something on behalf of another entity.
-
E.
isPremium
Indicates that an entity has premium status, typically granting enhanced or paid-tier features or privileges compared to a standard version.
- 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.