Triple
T33093494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slinky |
E846845
|
entity |
| Predicate | hasNotableDemonstrationPrice |
P17277
|
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, hasNotableDemonstrationPrice, 1 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDemonstrationPrice Context triple: [Slinky, hasNotableDemonstrationPrice, 1 USD]
-
A.
isValuePriced
chosen
Indicates that something is offered at a relatively low or favorable price compared to typical or premium alternatives.
-
B.
hasNotableDeal
Indicates that an entity is involved in a significant or noteworthy agreement, contract, or transaction with another entity.
-
C.
hasDemonstration
Indicates that one entity includes, is accompanied by, or is associated with a demonstration or illustrative example of another entity or concept.
-
D.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
E.
launchPriceDescription
Indicates the descriptive text explaining the initial price at which a product or service is first launched or offered.
- 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_6a017bc21b048190b9c680013de203b6 |
completed | May 11, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_6a017aa09c4481909c3b55e0cd13501e |
completed | May 11, 2026, 6:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.