Triple
T28008702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samson Brewery |
E707353
|
entity |
| Predicate | hasMainProductCategory |
P2767
|
FINISHED |
| Object | Bohemian lager |
—
|
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: Bohemian lager | Statement: [Samson Brewery, hasMainProductCategory, Bohemian lager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainProductCategory Context triple: [Samson Brewery, hasMainProductCategory, Bohemian lager]
-
A.
hasMajorCategory
chosen
Indicates that something is associated with or classified under a primary, overarching category.
-
B.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
C.
hasCategories
Indicates that an entity is associated with one or more categories that classify or group it.
-
D.
hasBodelCategory
Indicates that an entity is associated with a specific Bodel classification category within a defined categorization system.
-
E.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
Created at: April 27, 2026, 8:02 p.m.