Triple
T35063196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridget Lancaster |
E1011652
|
entity |
| Predicate | typeOfChef |
P50761
|
FINISHED |
| Object | television 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: television chef | Statement: [Bridget Lancaster, typeOfChef, television chef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfChef Context triple: [Bridget Lancaster, typeOfChef, television 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.
designerChef
Indicates that one entity serves as the chef responsible for designing or creating dishes, menus, or culinary concepts for another entity.
-
D.
visibilityOfChef
Indicates how easily or prominently a chef can be seen or observed in a given context or setting.
-
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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0186cde2fc819080d7c06503dcc479 |
completed | May 11, 2026, 7:35 a.m. |
| PD | Predicate disambiguation | batch_6a0183ff6d34819080c8ad7c11611a36 |
completed | May 11, 2026, 7:23 a.m. |
Created at: May 3, 2026, 4:01 p.m.