Triple
T28147463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chef! |
E714521
|
entity |
| Predicate | hasCuisineTheme |
P5786
|
FINISHED |
| Object | French 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: French cuisine | Statement: [Chef!, hasCuisineTheme, French cuisine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCuisineTheme Context triple: [Chef!, hasCuisineTheme, French cuisine]
-
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.
cuisineFeature
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
-
C.
cuisineType
chosen
Indicates the type or style of food associated with an entity, such as a restaurant or dish.
-
D.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
E.
hasCuisineRecognition
Indicates that an entity has received formal recognition, awards, or notable acknowledgment specifically for its 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_69efd6b033208190bf74f80a147e2092 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 9:57 p.m.