Triple
T32631616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tracy Griffith |
E834227
|
entity |
| Predicate | culinaryProfession |
P50761
|
FINISHED |
| Object | sushi chef |
—
|
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: sushi chef | Statement: [Tracy Griffith, culinaryProfession, sushi chef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: culinaryProfession Context triple: [Tracy Griffith, culinaryProfession, sushi chef]
-
A.
chefTitle
Indicates that one entity holds a specific professional or honorific title in the role of a chef relative to another entity.
-
B.
chef
chosen
Indicates that one entity serves as the cook or culinary professional responsible for preparing food for another entity or context.
-
C.
culinaryStatus
Indicates the current state or condition of something in relation to cooking or food preparation (e.g., raw, cooked, undercooked, burnt).
-
D.
culinaryPhilosophy
Indicates a guiding set of beliefs, values, or principles that shape how one approaches cooking, food, and eating.
-
E.
worksInKitchenAt
Indicates that an entity performs work or duties in the kitchen area of a specified location or organization.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:07 a.m.