Triple
T32726186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 英山云雾茶 |
E836808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 地理标志产品 |
C42799
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: 地理标志产品 Context triple: [英山云雾茶, instanceOf, 地理标志产品]
-
A.
geographically protected product
chosen
A geographically protected product is a good whose name and distinctive qualities are legally tied to a specific region, ensuring it can only be produced there under defined standards.
-
B.
地名
地名とは、地球上の特定の場所・地域・地形・施設などを識別し区別するために付けられた固有の名称である。
-
C.
protected geographical indication
A protected geographical indication is a designation used on products that have a specific quality, reputation, or other characteristic essentially attributable to their geographic origin, and whose production, processing, or preparation occurs in that defined area.
-
D.
geographical indication protection body
A geographical indication protection body is an organization responsible for recognizing, registering, and enforcing the rights associated with geographical indications to ensure that only products genuinely originating from a specific region can use its protected name.
-
E.
Appellation d’Origine Contrôlée product
An Appellation d’Origine Contrôlée product is a good—typically a food, wine, or spirit—whose name, production methods, and quality are legally protected and strictly regulated as originating from a specific geographic region in France.
- F. None of above.
Provenance (1 batch)
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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:11 a.m.