Triple
T37626764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daviess County Bourbon |
E936232
|
entity |
| Predicate | secondaryGrain |
P200679
|
FINISHED |
| Object | wheat |
—
|
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: wheat | Statement: [Daviess County Bourbon, secondaryGrain, wheat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryGrain Context triple: [Daviess County Bourbon, secondaryGrain, wheat]
-
A.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
B.
secondTier
Indicates that something occupies a secondary or subordinate level of importance, quality, or rank relative to a primary or top tier.
-
C.
secondaryGround
Indicates a secondary or auxiliary grounding connection or reference point associated with the primary ground.
-
D.
secondarySingle
Indicates that an entity serves as a secondary, but singular, counterpart or role in relation to another primary entity.
-
E.
secondaryConstituent
Indicates that one entity functions as a secondary or subordinate component, element, or member within the structure or composition of another entity.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69ff9e90b5248190bdd8d13f966b63e1 |
completed | May 9, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:18 p.m.