Triple
T34665108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jean Georges Steakhouse |
E890230
|
entity |
| Predicate | hasChef |
P50761
|
FINISHED |
| Object | Jean-Georges Vongerichten |
—
|
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: Jean-Georges Vongerichten | Statement: [Jean Georges Steakhouse, hasChef, Jean-Georges Vongerichten]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChef Context triple: [Jean Georges Steakhouse, hasChef, Jean-Georges Vongerichten]
-
A.
isCookedBy
Indicates that something has been prepared or made ready for eating through cooking by a particular agent.
-
B.
chef
chosen
Indicates that one entity serves as the cook or culinary professional responsible for preparing food for another entity or context.
-
C.
visibilityOfChef
Indicates how easily or prominently a chef can be seen or observed in a given context or setting.
-
D.
designerChef
Indicates that one entity serves as the chef responsible for designing or creating dishes, menus, or culinary concepts for another entity.
-
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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 1, 2026, 2:04 a.m.