Triple
T25746205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Continental Mark II |
E648349
|
entity |
| Predicate | priceNew |
P7794
|
FINISHED |
| Object | approximately US$10,000 in 1956 |
—
|
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: approximately US$10,000 in 1956 | Statement: [Continental Mark II, priceNew, approximately US$10,000 in 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priceNew Context triple: [Continental Mark II, priceNew, approximately US$10,000 in 1956]
-
A.
purchasePrice
chosen
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
-
B.
priceChange
Indicates a change in the price of an entity, typically specifying how much and/or in what direction the price has moved over a given period.
-
C.
laterPrice
Indicates that the price of an item at a later time is being specified or related to another (typically earlier) price.
-
D.
priceReference
Indicates a relationship where one price is used as a benchmark or basis for determining, comparing, or deriving another price.
-
E.
priceDeterminedBy
Indicates that the price of one entity is set, influenced, or calculated based on another entity or factor.
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd1fb8d88190a03c705fecf22634 |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 3:51 a.m.