Triple
T37192042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fasig-Tipton sales |
E921482
|
entity |
| Predicate | notableSaleType |
—
|
GENERATED |
| Object | yearling sale |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSaleType Context triple: [Fasig-Tipton sales, notableSaleType, yearling sale]
-
A.
saleType
chosen
Indicates the specific category or method by which a sale is conducted or classified (e.g., retail, wholesale, auction).
-
B.
subjectOfSale
Indicates that one entity is the item, asset, or right being transferred or offered in a sale transaction involving another entity.
-
C.
typeOfDeal
Indicates the specific category or nature of a deal or agreement that applies between entities.
-
D.
recordAtSale
Indicates that something is documented or captured at the time a sale transaction occurs.
-
E.
associatedSingleSales
Indicates that there is a specific, single sales record or transaction linked to the given entity.
- F. None of above.
Provenance (1 batch)
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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.