Triple
T22245581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plan N |
E549831
|
entity |
| Predicate | premiumsMay |
P147532
|
FINISHED |
| Object | vary by insurer |
—
|
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: vary by insurer | Statement: [Plan N, premiumsMay, vary by insurer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiumsMay Context triple: [Plan N, premiumsMay, vary by insurer]
-
A.
mayCover
Indicates that one entity is permitted or able to extend over, include, or provide coverage for another entity, either partially or fully.
-
B.
majorPremiumNetwork
Indicates that an entity is a primary or flagship premium network within a broader media or service ecosystem.
-
C.
typicallyCovers
Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses another entity.
-
D.
mayGuarantee
Indicates that one entity has the potential or authority to provide a guarantee for another entity or outcome.
-
E.
requiresPremiumFor
Indicates that access to or use of something is conditional on having a premium status, subscription, or account.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:38 p.m.