Triple
T12344305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christie’s |
E294308
|
entity |
| Predicate | hasNotableSale |
P24014
|
FINISHED |
| Object | sale of Leonardo da Vinci’s Salvator Mundi |
—
|
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: sale of Leonardo da Vinci’s Salvator Mundi | Statement: [Christie’s, hasNotableSale, sale of Leonardo da Vinci’s Salvator Mundi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSale Context triple: [Christie’s, hasNotableSale, sale of Leonardo da Vinci’s Salvator Mundi]
-
A.
hasNotableDeal
chosen
Indicates that an entity is involved in a significant or noteworthy agreement, contract, or transaction with another entity.
-
B.
soldWellIn
Indicates that something achieved strong sales performance within a particular market, region, or time period.
-
C.
soldAs
Indicates that one entity is marketed, offered, or presented to others under the name, form, or role of another entity.
-
D.
soldAt
Indicates that a product or item is offered for sale at a particular location, venue, or outlet.
-
E.
soldDuring
Indicates that a selling transaction or event occurred within the time span of a specified period or event.
- 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f78a970819086beec3e4da8c49e |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.