Triple
T16432346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harveys Brewery |
E399097
|
entity |
| Predicate | hasBreweryPlantType |
P53908
|
FINISHED |
| Object | tower brewery |
—
|
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: tower brewery | Statement: [Harveys Brewery, hasBreweryPlantType, tower brewery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBreweryPlantType Context triple: [Harveys Brewery, hasBreweryPlantType, tower brewery]
-
A.
hasBreweryOrFacility
Indicates that an entity possesses, operates, or is associated with a brewery or brewing-related facility.
-
B.
hasPlantCategory
Indicates that one entity is assigned to, or classified under, a particular plant-related category or type.
-
C.
hasCultivar
Indicates that one entity is a plant species or variety that possesses, includes, or is associated with a specific cultivated variety (cultivar) as another entity.
-
D.
breweryType
chosen
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
-
E.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32b9f2e8c81909c60b8fb78255e5f |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.