Triple
T32136108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raki |
E820766
|
entity |
| Predicate | regionallyAssociatedCuisine |
P12445
|
FINISHED |
| Object | Turkish cuisine |
—
|
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: Turkish cuisine | Statement: [Raki, regionallyAssociatedCuisine, Turkish cuisine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionallyAssociatedCuisine Context triple: [Raki, regionallyAssociatedCuisine, Turkish cuisine]
-
A.
regionOfCulinaryImportance
Indicates that a location is recognized for its significant culinary relevance, such as notable food traditions, specialties, or gastronomic culture.
-
B.
regionallyAssociatedWith
chosen
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
C.
includesRegionalCuisine
Indicates that one entity incorporates or features the regional cuisine associated with another entity.
-
D.
cuisineType
Indicates the type or style of food associated with an entity, such as a restaurant or dish.
-
E.
regionallyKnownAs
Indicates that an entity is known by a particular name or designation within a specific geographic region.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 1, 2026, 12:30 a.m.