Triple
T2956155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ion 2 |
E79935
|
entity |
| Predicate | trimLevelRelativePrice |
P35383
|
FINISHED |
| Object | mid-priced within Saturn Ion range |
—
|
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: mid-priced within Saturn Ion range | Statement: [Ion 2, trimLevelRelativePrice, mid-priced within Saturn Ion range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trimLevelRelativePrice Context triple: [Ion 2, trimLevelRelativePrice, mid-priced within Saturn Ion range]
-
A.
relativePrice
Indicates a comparison of the cost or monetary value of one entity relative to another.
-
B.
priceRelationship
Indicates a comparative relationship between the prices of two entities, such as one being higher, lower, or equal to the other.
-
C.
trimLevel
Indicates the specific configuration or package level of features or options applied to an item, typically distinguishing variants within the same base model.
-
D.
associatedWithPriceLevel
chosen
Indicates a relationship where something is linked or connected to a particular price level or pricing tier.
-
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_69ad8b1276588190a374a0b12e0f7bdf |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad992998f08190ac9428310983172e |
completed | March 8, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69ad960c5c8881909d679912bd7d78f3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:57 p.m.