Triple
T19578558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgogi |
E489924
|
entity |
| Predicate | typicalMarinadeIngredient |
P12771
|
FINISHED |
| Object | soy sauce |
—
|
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: soy sauce | Statement: [Bulgogi, typicalMarinadeIngredient, soy sauce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMarinadeIngredient Context triple: [Bulgogi, typicalMarinadeIngredient, soy sauce]
-
A.
ingredientType
Indicates that one entity is classified as a specific type or category of ingredient in relation to another.
-
B.
typicalIngredientRatio
Indicates the usual proportional relationship between different ingredients used together in a preparation or mixture.
-
C.
typicalSpices
Indicates that certain spices are commonly or characteristically used in association with a particular dish, cuisine, or ingredient.
-
D.
usesIngredient
chosen
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
-
E.
isTypicallyGarnishedWith
Indicates that one item is commonly used as a garnish or decorative finishing element for another.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402693d88190a828c0e136895783 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.