Triple
T38541934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China Resources Snow Breweries |
E924854
|
entity |
| Predicate | hasDomesticBrandFocus |
P162908
|
FINISHED |
| Object | Snow Beer |
—
|
NE NERFINISHED |
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: Snow Beer | Statement: [China Resources Snow Breweries, hasDomesticBrandFocus, Snow Beer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomesticBrandFocus Context triple: [China Resources Snow Breweries, hasDomesticBrandFocus, Snow Beer]
-
A.
hasGlobalBrand
Indicates that an entity possesses a brand that is recognized and operates across multiple countries or worldwide.
-
B.
hasBrandSpecialization
chosen
Indicates that an entity focuses on, is tailored to, or primarily serves a specific brand or set of brands.
-
C.
hasBrandArchitecture
Indicates that one entity defines, structures, or governs the brand architecture (the organized system of brands, sub-brands, and their relationships) of another entity.
-
D.
hasNotableSubBrand
Indicates that an entity includes or owns a distinct, well-known sub-brand associated with it.
-
E.
parentBrandCountry
Indicates that a brand’s parent company is based in or associated with a specific country.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:32 p.m.