Triple
T1452324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Celeron |
E31318
|
entity |
| Predicate | priceLevelComparedTo |
P9543
|
FINISHED |
| Object | cheaper than Intel Pentium |
—
|
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: cheaper than Intel Pentium | Statement: [Intel Celeron, priceLevelComparedTo, cheaper than Intel Pentium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priceLevelComparedTo Context triple: [Intel Celeron, priceLevelComparedTo, cheaper than Intel Pentium]
-
A.
priceRelationship
Indicates a comparative relationship between the prices of two entities, such as one being higher, lower, or equal to the other.
-
B.
relativePrice
chosen
Indicates a comparison of the cost or monetary value of one entity relative to another.
-
C.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
D.
priceReference
Indicates a relationship where one price is used as a benchmark or basis for determining, comparing, or deriving another price.
-
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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c57d34cc8190801b769d9d9b2e2e |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47cdbd0819092022344a2f4ad7b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.