Triple
T1870035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macintosh LC |
E39011
|
entity |
| Predicate | targetPriceAtLaunch |
P32176
|
FINISHED |
| Object | around US$2,400 with 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: around US$2,400 with monitor | Statement: [Macintosh LC, targetPriceAtLaunch, around US$2,400 with monitor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPriceAtLaunch Context triple: [Macintosh LC, targetPriceAtLaunch, around US$2,400 with monitor]
-
A.
actualLaunchPrice
Indicates the price at which something was actually launched or first offered, as opposed to its planned or advertised launch price.
-
B.
launchPriceDescription
chosen
Indicates the descriptive text explaining the initial price at which a product or service is first launched or offered.
-
C.
launchPriceRegion
Indicates the geographic region or market in which a product’s initial launch price applies.
-
D.
purchasePrice
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
-
E.
initialPriceTarget
Indicates the originally set price level that an analyst or entity targets for an asset before any subsequent revisions.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0f79fbc819085c54f3189a552d9 |
completed | March 7, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69abafe2b56c81909e13d543982e6e13 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.