Triple
T234659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The New York Times |
E4481
|
entity |
| Predicate | digitalSubscriptionModel |
P628
|
FINISHED |
| Object | 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: paywall | Statement: [The New York Times, digitalSubscriptionModel, paywall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: digitalSubscriptionModel Context triple: [The New York Times, digitalSubscriptionModel, paywall]
-
A.
edition
Indicates that one entity is a specific version, issue, or release of another (typically a work such as a book, journal, or software).
-
B.
publishingModel
chosen
Indicates the method or framework by which content is produced, distributed, and made publicly available.
-
C.
nextEdition
Indicates that one entity is the immediate subsequent edition or version that follows another in a sequence.
-
D.
fareMedia
Indicates that a particular type of ticket, pass, or payment instrument is used as the medium for paying a fare.
-
E.
publishedIn
Indicates that a work (such as an article, paper, or book) has been formally released or made available within a specific venue, medium, or publication.
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f14f72081908182e76300b59358 |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b5c8c888190b5544e687736b373 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.