Triple
T4426306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medium |
E95216
|
entity |
| Predicate | hasPaywall |
P21228
|
FINISHED |
| Object | metered paywall |
—
|
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: metered paywall | Statement: [Medium, hasPaywall, metered paywall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaywall Context triple: [Medium, hasPaywall, metered paywall]
-
A.
hasPaymentOption
Indicates that an entity supports or offers a particular method or option for making payments.
-
B.
hasDigitalSubscription
Indicates that one entity holds an active digital subscription to a service, product, or content provided by another entity.
-
C.
hasPaymentModel
chosen
Indicates that an entity uses, is associated with, or operates under a particular payment model or pricing scheme.
-
D.
hasPayStatus
Indicates the current payment state or condition associated with an entity, such as whether an amount is paid, unpaid, pending, or otherwise resolved.
-
E.
hasInAppPurchases
Indicates that an application offers additional content, features, or services that users can buy from within the app itself.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554fb28081909018eaecc0c5c230 |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.