Triple
T26041088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris |
E647691
|
entity |
| Predicate | intendedPriceSegment |
P69282
|
FINISHED |
| Object | low price |
—
|
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: low price | Statement: [Paris, intendedPriceSegment, low price]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedPriceSegment Context triple: [Paris, intendedPriceSegment, low price]
-
A.
hasTargetPriceSegment
chosen
Indicates that something is associated with or assigned to a specific target price range or pricing segment.
-
B.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
C.
priceCategory
Indicates the classification of an item or service based on its price level or cost range.
-
D.
intendedSegment
Indicates that one entity is the target or designated recipient segment for another entity (such as a message, offer, or action).
-
E.
priceType
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 22, 2026, 9:08 a.m.