Triple
T25020961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tteokbokki |
E626566
|
entity |
| Predicate | traditionalVersionFlavor |
P164970
|
FINISHED |
| Object | soy sauce-based |
—
|
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-based | Statement: [tteokbokki, traditionalVersionFlavor, soy sauce-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalVersionFlavor Context triple: [tteokbokki, traditionalVersionFlavor, soy sauce-based]
-
A.
traditionalStyle
Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
-
B.
traditionalBase
Indicates that one entity serves as the customary or historically established foundation or basis for another.
-
C.
traditionalFat
Indicates that an entity uses or contains a type or amount of fat characteristic of customary or long-established practices.
-
D.
traditionalView
Indicates that one entity holds or represents a conventional, long-established perspective or interpretation about another entity or topic.
-
E.
traditionalStatus
Indicates that one entity holds a customary, long-established, or culturally recognized role, condition, or standing in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 18, 2026, 6:06 a.m.