Triple
T22441233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | water-boiled beef |
E554758
|
entity |
| Predicate | seasoningFeature |
P62832
|
FINISHED |
| Object | heavy use of chili |
—
|
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: heavy use of chili | Statement: [water-boiled beef, seasoningFeature, heavy use of chili]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasoningFeature Context triple: [water-boiled beef, seasoningFeature, heavy use of chili]
-
A.
seasoningType
Indicates the specific kind or category of seasoning associated with an item or preparation.
-
B.
seasoningStyle
chosen
Indicates the characteristic way in which an item is flavored or seasoned, such as the method, intensity, or cultural style of its seasoning.
-
C.
cuisineFeature
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
-
D.
isTypicallyGarnishedWith
Indicates that one item is commonly used as a garnish or decorative finishing element for another.
-
E.
typicalSpices
Indicates that certain spices are commonly or characteristically used in association with a particular dish, cuisine, or ingredient.
- 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.