Triple
T29119116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American pulp magazines |
E737128
|
entity |
| Predicate | typicalPrice |
P66659
|
FINISHED |
| Object | inexpensive mass-market |
—
|
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: inexpensive mass-market | Statement: [American pulp magazines, typicalPrice, inexpensive mass-market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPrice Context triple: [American pulp magazines, typicalPrice, inexpensive mass-market]
-
A.
typicalRate
Indicates the standard or commonly expected rate at which something occurs, is charged, or is applied in a given context.
-
B.
typicalLaunchPrice
Indicates the usual or standard price at which something is initially offered or launched.
-
C.
priceType
chosen
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
-
D.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
E.
priceInfluencedBy
Indicates that the price of one entity is affected or determined by another specified factor or entity.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a017e7bdfe481909cb4d5bdede6035e |
completed | May 11, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_6a017defee108190bdf5f98dc415b250 |
completed | May 11, 2026, 6:57 a.m. |
Created at: April 28, 2026, 11:24 a.m.