Triple
T615780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Lisa |
E14399
|
entity |
| Predicate | originalPrice |
P17161
|
FINISHED |
| Object | 9995 USD |
—
|
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: 9995 USD | Statement: [Apple Lisa, originalPrice, 9995 USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalPrice Context triple: [Apple Lisa, originalPrice, 9995 USD]
-
A.
purchasePrice
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
-
B.
actualLaunchPrice
Indicates the price at which something was actually launched or first offered, as opposed to its planned or advertised launch price.
-
C.
acquisitionPrice
Indicates the monetary amount paid to acquire an asset, company, or item in a transaction.
-
D.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
-
E.
priceReference
Indicates a relationship where one price is used as a benchmark or basis for determining, comparing, or deriving another price.
- F. None of above. chosen
Provenance (4 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e0b438881909ad515adf7a4eb79 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfbcbf88190a854921dc531eba8 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49def31ec81909dc53e70f4a36eda |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.