Triple
T28264202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Old Reader |
E712656
|
entity |
| Predicate | premiumPlanIncludes |
P124299
|
FINISHED |
| Object | higher subscription limits |
—
|
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: higher subscription limits | Statement: [The Old Reader, premiumPlanIncludes, higher subscription limits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: premiumPlanIncludes Context triple: [The Old Reader, premiumPlanIncludes, higher subscription limits]
-
A.
paidTierIncludes
chosen
Indicates that a paid subscription tier encompasses or provides access to a specified feature, service, or benefit.
-
B.
promotionIncludes
Indicates that a particular promotion encompasses, covers, or applies to a specified item, service, or condition.
-
C.
requiresPremiumFor
Indicates that access to or use of something is conditional on having a premium status, subscription, or account.
-
D.
offersFeature
Indicates that one entity provides or makes available a particular feature or capability to another entity.
-
E.
productIncludes
Indicates that a product contains, comprises, or is composed of the specified component, item, or feature.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 11:13 p.m.