Triple
T32726197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 英山云雾茶 |
E836808
|
entity |
| Predicate | 原料 |
P5629
|
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: [英山云雾茶, 原料, 一芽一叶或一芽二叶嫩芽叶]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 原料 Context triple: [英山云雾茶, 原料, 一芽一叶或一芽二叶嫩芽叶]
-
A.
materialSource
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
B.
originalMaterialFor
Indicates that one entity serves as the source or basis material from which another entity is derived, adapted, or created.
-
C.
originalCoreMaterial
Indicates that something is made from or based on the initial, primary material used before any changes, replacements, or modifications.
-
D.
primaryFeedstock
chosen
Indicates that one entity serves as the main raw material or input used to produce, process, or operate another entity.
-
E.
ingredientOrigin
Indicates that an ingredient comes from, is sourced in, or originates from a particular place or source.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8b80b508190b03c5a5859c695fe |
completed | May 3, 2026, 4:02 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.