Triple
T19578582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgogi |
E489924
|
entity |
| Predicate | oftenCookedOn |
P61222
|
FINISHED |
| Object | tabletop grill |
—
|
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: tabletop grill | Statement: [Bulgogi, oftenCookedOn, tabletop grill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCookedOn Context triple: [Bulgogi, oftenCookedOn, tabletop grill]
-
A.
isUsuallyCookedIn
chosen
Indicates that something is most commonly or typically prepared or cooked within a particular container, appliance, or environment.
-
B.
isCookedBy
Indicates that something has been prepared or made ready for eating through cooking by a particular agent.
-
C.
isNotCookedOn
Indicates that one entity is not prepared or heated using another entity as the cooking surface, method, or medium.
-
D.
culinaryStatus
Indicates the current state or condition of something in relation to cooking or food preparation (e.g., raw, cooked, undercooked, burnt).
-
E.
isOftenHomemade
Indicates that something is frequently made at home rather than being purchased or produced commercially.
- 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.