Triple
T32726209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 英山云雾茶 |
E836808
|
entity |
| Predicate | 香气 |
P152625
|
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.
characteristicAroma
chosen
Indicates that one entity has a distinctive smell or scent that characterizes or is typically associated with another entity.
-
B.
魅力
Indicates that one entity possesses an attractive quality or charm that draws interest, admiration, or affection from others.
-
C.
fragranceInspiration
Indicates that one entity serves as the creative or conceptual inspiration behind the fragrance of another entity.
-
D.
commonScents
Indicates that two or more entities share the same or very similar smells or fragrances.
-
E.
olfactoryStyle
Indicates a relationship where one entity’s characteristic way of perceiving, using, or expressing smell is associated with or attributed to another entity.
- 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.