Triple
T34232621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sazerac Rye |
E878243
|
entity |
| Predicate | typicalProof |
—
|
GENERATED |
| Object | 90 proof |
—
|
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: typicalProof Context triple: [Sazerac Rye, typicalProof, 90 proof]
-
A.
typicalProofUses
Indicates that a proof characteristically or commonly employs a particular method, technique, or component.
-
B.
provedFrom
Indicates that one statement, theorem, or conclusion is logically derived and demonstrated to be true based on another statement or set of premises.
-
C.
provesTo
Indicates that one entity demonstrates or establishes the truth or validity of something to another entity.
-
D.
typicalConclusion
Indicates that one entity is the usual or expected outcome, result, or ending that follows from another entity or situation.
-
E.
partialProofBy
Indicates that one entity serves as an incomplete or intermediate proof contributing toward the full proof of another entity.
- F. None of above. chosen
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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:56 a.m.