Triple
T21482111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Jones |
E530017
|
entity |
| Predicate | kitchenRole |
P50761
|
FINISHED |
| Object | executive 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: executive chef | Statement: [Adam Jones, kitchenRole, executive chef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kitchenRole Context triple: [Adam Jones, kitchenRole, executive chef]
-
A.
roleInFood
Indicates the functional role or purpose that an entity has within a food item, product, or context (e.g., ingredient, flavoring, preservative).
-
B.
chef
chosen
Indicates that one entity serves as the cook or culinary professional responsible for preparing food for another entity or context.
-
C.
houseRole
Indicates the functional role, purpose, or use that a house has within a given context or system.
-
D.
householdStaff
Indicates that one entity serves as domestic or household staff for another entity, typically within a private residence.
-
E.
roleInCoco
Indicates that an entity serves a specific role or function within the context of the COCO dataset or framework.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea34c4388190adc78d209d2aafb8 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:21 p.m.