Triple
T2016863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pueblo chile |
E44013
|
entity |
| Predicate | hasCulinaryRole |
P17589
|
FINISHED |
| Object | signature ingredient of Pueblo, Colorado |
—
|
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: signature ingredient of Pueblo, Colorado | Statement: [Pueblo chile, hasCulinaryRole, signature ingredient of Pueblo, Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulinaryRole Context triple: [Pueblo chile, hasCulinaryRole, signature ingredient of Pueblo, Colorado]
-
A.
isCookedBy
Indicates that something has been prepared or made ready for eating through cooking by a particular agent.
-
B.
hasSpecialtyFood
Indicates that an entity offers, serves, or is associated with a particular type of specialty food.
-
C.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
D.
hasCuisineItem
chosen
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
E.
hasCookingQuality
Indicates that something possesses a particular characteristic or attribute related to cooking, such as flavor, texture, or suitability for a cooking method.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8ccdb7c81909f6b3c96f79fcdfc |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.