Triple
T34412559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonel E.H. Taylor Jr. Bourbon |
E883312
|
entity |
| Predicate | grainRequirement |
P32631
|
FINISHED |
| Object | at least 51% corn |
—
|
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: at least 51% corn | Statement: [Colonel E.H. Taylor Jr. Bourbon, grainRequirement, at least 51% corn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grainRequirement Context triple: [Colonel E.H. Taylor Jr. Bourbon, grainRequirement, at least 51% corn]
-
A.
grain
Indicates that one entity is composed of or contains a granular substance or small particles of another entity.
-
B.
hasGrainQuality
Indicates that an entity possesses a particular level or type of grain quality, characterizing the quality attributes of its grain.
-
C.
hasGrainType
chosen
Indicates that an entity is characterized by or associated with a specific type of grain.
-
D.
feedingRequirement
Indicates that one entity has a specified need or condition related to how, when, or what it must be fed by another entity.
-
E.
granaryType
Indicates the specific kind or category of granary associated with or used by an entity.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71947ad88819082ab9d85dd493b01 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.