Triple

T5984943
Position Surface form Disambiguated ID Type / Status
Subject sundubu jjigae E133203 entity
Predicate traditionalCookingVessel P61222 FINISHED
Object ttukbaegi 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: ttukbaegi | Statement: [sundubu jjigae, traditionalCookingVessel, ttukbaegi]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionalCookingVessel
Context triple: [sundubu jjigae, traditionalCookingVessel, ttukbaegi]
  • A. traditionalVessel
    Indicates that one entity is a vessel or container that follows traditional, customary, or historically established forms, designs, or uses in relation to another entity.
  • B. possibleFermentationVessel
    Indicates that something can serve as a suitable container or environment in which fermentation may take place.
  • C. dishType
    Indicates the classification of a dish according to its culinary category or role (e.g., appetizer, main course, dessert).
  • D. isUsuallyCookedIn chosen
    Indicates that something is most commonly or typically prepared or cooked within a particular container, appliance, or environment.
  • E. traditionalDish
    Indicates that the object is a dish customarily prepared, eaten, or recognized within the subject’s cultural or regional tradition.
  • 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_69c0087010d081908bb8142342d63330 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04a6dcaf08190bac27c7042e65e07 completed March 22, 2026, 8 p.m.
PD Predicate disambiguation batch_69c049de98648190962b14fd341c93da completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:04 p.m.