Triple
T27793812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ga Traditional Area |
E701150
|
entity |
| Predicate | hasCulturalFood |
P89569
|
FINISHED |
| Object | kpokpoi |
—
|
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: kpokpoi | Statement: [Ga Traditional Area, hasCulturalFood, kpokpoi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalFood Context triple: [Ga Traditional Area, hasCulturalFood, kpokpoi]
-
A.
haveCuisine
Indicates that an entity (such as a restaurant or place) offers, serves, or is associated with a particular type or style of cuisine.
-
B.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
C.
hasFeastTraditionWith
Indicates a relationship where two entities share or participate in a customary feast or celebratory meal tradition together.
-
D.
hasSpecialtyFood
Indicates that an entity offers, serves, or is associated with a particular type of specialty food.
-
E.
foodCulture
chosen
Indicates the relationship between a place or group and its characteristic traditions, practices, and preferences surrounding food and eating.
- 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 27, 2026, 5:29 p.m.