Triple
T21570478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPC464 |
E532267
|
entity |
| Predicate | releasePriceRegion |
P32175
|
FINISHED |
| Object | £199 with green monitor |
—
|
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: £199 with green monitor | Statement: [CPC464, releasePriceRegion, £199 with green monitor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasePriceRegion Context triple: [CPC464, releasePriceRegion, £199 with green monitor]
-
A.
launchPriceRegion
chosen
Indicates the geographic region or market in which a product’s initial launch price applies.
-
B.
releaseRegion
Indicates the geographic or jurisdictional area in which something (such as a product, service, or content) is made available or officially released.
-
C.
availableInCountry
Indicates that something can be legally or practically obtained, accessed, or used within a specified country.
-
D.
regionExclusiveAtLaunch
Indicates that something was initially available only within a specific geographic region at the time of its launch.
-
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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cc5c448190887a836f577d01ba |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:30 p.m.