Triple
T13595065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tales to Astonish #27 |
E324796
|
entity |
| Predicate | coverPrice |
P17161
|
FINISHED |
| Object | $0.12 |
—
|
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: $0.12 | Statement: [Tales to Astonish #27, coverPrice, $0.12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverPrice Context triple: [Tales to Astonish #27, coverPrice, $0.12]
-
A.
originalPrice
chosen
Indicates the monetary amount that something initially cost before any discounts, changes, or adjustments were applied.
-
B.
cover
Indicates that one entity extends over, conceals, protects, or provides a surface or layer for another entity.
-
C.
purchasePrice
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
-
D.
priceInFiction
Indicates the monetary cost or value assigned to something within a fictional or imaginary context.
-
E.
coverText
Indicates that one text serves as the cover or front-facing textual representation for another work or resource.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb057f1c881909a3bb77c659a724a |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.