Triple
T37192056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fasig-Tipton sales |
E921482
|
entity |
| Predicate | buyerBase |
P114201
|
FINISHED |
| Object | domestic buyers |
—
|
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: domestic buyers | Statement: [Fasig-Tipton sales, buyerBase, domestic buyers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buyerBase Context triple: [Fasig-Tipton sales, buyerBase, domestic buyers]
-
A.
buyer
Indicates a relationship where one entity purchases or acquires goods, services, or rights from another entity in exchange for payment or compensation.
-
B.
buyIn
Indicates that one party purchases or acquires an ownership stake, participation, or commitment in something initiated or owned by another party.
-
C.
buys
Indicates that one entity purchases or acquires something from another entity, typically in exchange for money or other compensation.
-
D.
purchaseContext
chosen
Indicates the circumstances, conditions, or situational details under which a purchase occurs or is made.
-
E.
bargainsFor
Indicates that one entity negotiates or seeks to obtain another entity, typically aiming for more favorable terms or conditions.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.