Triple
T28553141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | künefe |
E722939
|
entity |
| Predicate | originatesFromCuisine |
P133695
|
FINISHED |
| Object | Turkish cuisine |
—
|
NE NERFINISHED |
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: Turkish cuisine | Statement: [künefe, originatesFromCuisine, Turkish cuisine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromCuisine Context triple: [künefe, originatesFromCuisine, Turkish cuisine]
-
A.
originCountryCuisine
Indicates that a cuisine originates from or is traditionally associated with a particular country.
-
B.
hasCulinaryOrigin
chosen
Indicates that something originates from, or is traditionally associated with, a particular culinary tradition, cuisine, or food culture.
-
C.
placeOfOrigin
Indicates the location or source from which an entity originally comes or was created.
-
D.
cooksCuisine
Indicates that a person or agent prepares or specializes in making a particular type of cuisine.
-
E.
haveCuisine
Indicates that an entity (such as a restaurant or place) offers, serves, or is associated with a particular type or style of cuisine.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: April 28, 2026, 3:44 a.m.