Triple
T15739730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Château Lafite Rothschild |
E381569
|
entity |
| Predicate | auctionPresence |
P120428
|
FINISHED |
| Object | frequently sold at fine wine auctions |
—
|
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: frequently sold at fine wine auctions | Statement: [Château Lafite Rothschild, auctionPresence, frequently sold at fine wine auctions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: auctionPresence Context triple: [Château Lafite Rothschild, auctionPresence, frequently sold at fine wine auctions]
-
A.
auctionMethod
Indicates the type or procedure of auction used to conduct a sale or bidding process between parties.
-
B.
auctionRecord
Indicates that there exists a documented record of an auction event involving the related entities.
-
C.
auctionCategory
Indicates that an item is classified under a specific auction category or type within an auction system.
-
D.
openingAuction
Indicates that an entity participates in, is associated with, or is defined in the context of an opening auction event or process.
-
E.
auctionDate
Indicates the date on which an auction is scheduled to occur or actually takes place.
- 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_69d86d9cdb648190bf3171be0bd7d872 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0b4d01c9c81909f6b611e8144c838 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 10, 2026, 4:46 a.m.