Triple
T22441439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuxiang eggplant |
E554762
|
entity |
| Predicate | originOfFlavorProfile |
P69349
|
FINISHED |
| Object | yuxiang 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: yuxiang flavor | Statement: [Yuxiang eggplant, originOfFlavorProfile, yuxiang flavor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originOfFlavorProfile Context triple: [Yuxiang eggplant, originOfFlavorProfile, yuxiang flavor]
-
A.
flavorProfileChangeWithAge
Indicates how the flavor characteristics of something evolve or change as it ages.
-
B.
flavorDevelopment
Indicates the process by which the taste characteristics of something change or intensify over time or through specific conditions or treatments.
-
C.
hasCulinaryOrigin
Indicates that something originates from, or is traditionally associated with, a particular culinary tradition, cuisine, or food culture.
-
D.
intendedFlavorProfile
Indicates the flavor characteristics that something is designed or planned to have, rather than what it actually tastes like.
-
E.
hasTastingProfile
chosen
Indicates that an entity possesses a specific flavor or sensory profile, typically describing its characteristic tastes and aromas.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae1f82881908a611f134eb03f3d |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.