Triple
T34068648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagle Rare Bourbon |
E873702
|
entity |
| Predicate | hasAllocatedDistribution |
P194325
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eagle Rare Bourbon, hasAllocatedDistribution, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAllocatedDistribution Context triple: [Eagle Rare Bourbon, hasAllocatedDistribution, true]
-
A.
hasAllocation
chosen
Indicates that a resource, amount, or portion has been assigned or distributed to a particular entity or purpose.
-
B.
hasDistributionType
Indicates the type or pattern of distribution associated with an entity, specifying how something is spread, allocated, or made available.
-
C.
hasRoleDistribution
Indicates how roles, responsibilities, or functions are allocated or distributed among entities within a given context.
-
D.
hasAllocatedTime
Indicates that a specific amount or period of time has been reserved or assigned for a particular entity, task, or activity.
-
E.
hasDistributedWorkOf
Indicates that an entity has assigned, allocated, or spread a particular work, task, or workload to another entity for execution or handling.
- 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_69f349a4af208190afa14888f9c9fb9d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 1, 2026, 1:52 a.m.