Triple
T22938585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solvang, California |
E569654
|
entity |
| Predicate | localCuisineSpecialty |
P17971
|
FINISHED |
| Object | Danish pastries |
—
|
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: Danish pastries | Statement: [Solvang, California, localCuisineSpecialty, Danish pastries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localCuisineSpecialty Context triple: [Solvang, California, localCuisineSpecialty, Danish pastries]
-
A.
hasSpecialtyFood
chosen
Indicates that an entity offers, serves, or is associated with a particular type of specialty food.
-
B.
cuisineFeature
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
-
C.
includesRegionalCuisine
Indicates that one entity incorporates or features the regional cuisine associated with another entity.
-
D.
foodCulture
Indicates the relationship between a place or group and its characteristic traditions, practices, and preferences surrounding food and eating.
-
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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181378660819083239986c846ec17 |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:45 p.m.