Triple
T27808765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teochew beef hotpot |
E702461
|
entity |
| Predicate | flavorEmphasis |
P90711
|
FINISHED |
| Object | natural beef flavor |
—
|
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: natural beef flavor | Statement: [Teochew beef hotpot, flavorEmphasis, natural beef flavor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flavorEmphasis Context triple: [Teochew beef hotpot, flavorEmphasis, natural beef flavor]
-
A.
typicalFlavor
Indicates that something characteristically has or is associated with a particular flavor.
-
B.
isFlavored
Indicates that one entity imparts a particular taste or flavor characteristic to another entity.
-
C.
primaryFlavor
chosen
Indicates the dominant or most characteristic taste associated with an item relative to other possible flavors.
-
D.
intendedFlavorProfile
Indicates the flavor characteristics that something is designed or planned to have, rather than what it actually tastes like.
-
E.
flavorDevelopment
Indicates the process by which the taste characteristics of something change or intensify over time or through specific conditions or treatments.
- 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_69ef840a16748190926719ab96120bae |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:41 p.m.