Triple
T33093495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slinky |
E846845
|
entity |
| Predicate | hasOriginalRetailPrice |
P17161
|
FINISHED |
| Object | 1 USD |
—
|
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: 1 USD | Statement: [Slinky, hasOriginalRetailPrice, 1 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalRetailPrice Context triple: [Slinky, hasOriginalRetailPrice, 1 USD]
-
A.
originalPrice
chosen
Indicates the monetary amount that something initially cost before any discounts, changes, or adjustments were applied.
-
B.
originalPriceModel
Indicates the pricing relationship that specifies an item's initial or base price before any discounts, adjustments, or dynamic pricing are applied.
-
C.
actualLaunchPrice
Indicates the price at which something was actually launched or first offered, as opposed to its planned or advertised launch price.
-
D.
hasOriginalsBrand
Indicates that one entity is associated with, or belongs to, the Originals brand of another entity.
-
E.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
Created at: May 1, 2026, 1:26 a.m.