Triple
T7110316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Actopan |
E165690
|
entity |
| Predicate | hasCuisineFeature |
P17157
|
FINISHED |
| Object | traditional Mexican dishes |
—
|
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: traditional Mexican dishes | Statement: [Actopan, hasCuisineFeature, traditional Mexican dishes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCuisineFeature Context triple: [Actopan, hasCuisineFeature, traditional Mexican dishes]
-
A.
cuisineFeature
chosen
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
-
B.
haveCuisine
Indicates that an entity (such as a restaurant or place) offers, serves, or is associated with a particular type or style of cuisine.
-
C.
hasCuisineItem
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
-
D.
hasDiningFeature
Indicates that something possesses a specific characteristic, amenity, or attribute related to dining.
-
E.
hasSpecialtyFood
Indicates that an entity offers, serves, or is associated with a particular type of specialty food.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5be09d881909988b5382ffa20ed |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.