Triple
T37492006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snow Beer |
E931714
|
entity |
| Predicate | brandNameInChineseCharacters |
P188395
|
FINISHED |
| Object | 雪花啤酒 |
—
|
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: 雪花啤酒 | Statement: [Snow Beer, brandNameInChineseCharacters, 雪花啤酒]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandNameInChineseCharacters Context triple: [Snow Beer, brandNameInChineseCharacters, 雪花啤酒]
-
A.
usesBrandCharacter
Indicates that one entity employs or features another entity’s brand character (such as a mascot or branded persona) in its materials, products, or communications.
-
B.
brandNameType
Indicates the specific type or category associated with a brand name within a broader branding or naming system.
-
C.
brandNumber
Indicates the identifying number or code assigned to a particular brand within a system or dataset.
-
D.
brandNameRefersTo
Indicates that a given brand name is used to denote or refer to a specific entity, product, or organization.
-
E.
brandNameUsedIn
Indicates that a particular brand name is used or appears within a specified context, such as a product, document, or communication.
- F. None of above. chosen
Provenance (4 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.