Triple
T16745556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Creoles |
E406941
|
entity |
| Predicate | cuisineAssociation |
P6863
|
FINISHED |
| Object | Creole 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: Creole cuisine | Statement: [White Creoles, cuisineAssociation, Creole cuisine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cuisineAssociation Context triple: [White Creoles, cuisineAssociation, Creole cuisine]
-
A.
cuisineType
Indicates the type or style of food associated with an entity, such as a restaurant or dish.
-
B.
knownForDish
Indicates that an entity is recognized or notable for preparing, serving, or being associated with a particular dish.
-
C.
sharesCuisineWith
Indicates that two entities offer or are associated with the same type or style of cuisine.
-
D.
regionOfCulinaryImportance
Indicates that a location is recognized for its significant culinary relevance, such as notable food traditions, specialties, or gastronomic culture.
-
E.
cuisine
chosen
Indicates the type or style of food traditionally associated with or served by an entity (such as a restaurant or 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa223aa88190a3c1805ece7317e2 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.