Triple
T30312751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | chicken tempura (toriten) |
E770969
|
entity |
| Predicate | typicallySeasonedWith |
P137544
|
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: [chicken tempura (toriten), typicallySeasonedWith, soy sauce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallySeasonedWith Context triple: [chicken tempura (toriten), typicallySeasonedWith, soy sauce]
-
A.
seasoningType
chosen
Indicates the specific kind or category of seasoning associated with an item or preparation.
-
B.
seasoningStyle
Indicates the characteristic way in which an item is flavored or seasoned, such as the method, intensity, or cultural style of its seasoning.
-
C.
isTypicallyGarnishedWith
Indicates that one item is commonly used as a garnish or decorative finishing element for another.
-
D.
isSavory
Indicates that something has a salty, spicy, or umami-dominant taste rather than a sweet one.
-
E.
traditionallyServed
Indicates that one entity is customarily or conventionally presented, offered, or consumed together with 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:50 p.m.