Triple
T27730627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deals with Gold |
E697420
|
entity |
| Predicate | purchaseType |
P66539
|
FINISHED |
| Object | digital purchase only |
—
|
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: digital purchase only | Statement: [Deals with Gold, purchaseType, digital purchase only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purchaseType Context triple: [Deals with Gold, purchaseType, digital purchase only]
-
A.
purchaseContext
Indicates the circumstances, conditions, or situational details under which a purchase occurs or is made.
-
B.
purchaseMethod
chosen
Indicates the way or channel through which a purchase is made (e.g., online, in-store, by phone, or via a specific payment or ordering method).
-
C.
buyIn
Indicates that one party purchases or acquires an ownership stake, participation, or commitment in something initiated or owned by another party.
-
D.
saleType
Indicates the specific category or method by which a sale is conducted or classified (e.g., retail, wholesale, auction).
-
E.
purchasePrice
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6369b658c8190bc6d697b9a4d5c03 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 3:11 p.m.