Triple
T1159558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cajun cuisine |
E24462
|
entity |
| Predicate | cookingTechnique |
P14777
|
FINISHED |
| Object | one-pot cooking |
—
|
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: one-pot cooking | Statement: [Cajun cuisine, cookingTechnique, one-pot cooking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cookingTechnique Context triple: [Cajun cuisine, cookingTechnique, one-pot cooking]
-
A.
usesCookingMethod
chosen
Indicates that one entity prepares or processes another entity by applying a specific cooking technique or method.
-
B.
cuisine
Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or region).
-
C.
cuisineFeature
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
-
D.
traditionalCuisine
Indicates that an entity is associated with the customary or historically rooted style of cooking and food preparation characteristic of a particular culture, region, or community.
-
E.
requiresCookingTemperature
Indicates that performing the action or preparing the item necessitates reaching or maintaining a specific cooking temperature.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcad47a08190895769611798f67f |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.