Triple
T7537731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salvadoran diaspora |
E178190
|
entity |
| Predicate | notableCuisineItem |
P17589
|
FINISHED |
| Object | pupusas |
—
|
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: pupusas | Statement: [Salvadoran diaspora, notableCuisineItem, pupusas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCuisineItem Context triple: [Salvadoran diaspora, notableCuisineItem, pupusas]
-
A.
isNationalDishOf
Indicates that a particular food is officially or culturally recognized as the national dish of a specific country or region.
-
B.
notableMeatProduct
Indicates that one entity is a meat-based product that is especially prominent, well-known, or significant in relation to the other entity.
-
C.
cuisineFeature
Indicates a characteristic, quality, or notable aspect that describes or distinguishes a particular cuisine.
-
D.
traditionalDish
Indicates that the object is a dish customarily prepared, eaten, or recognized within the subject’s cultural or regional tradition.
-
E.
hasCuisineItem
chosen
Indicates that a particular cuisine includes, features, or is associated with a specific food item.
- 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_69c69f2be3888190a6667a27f8f195e9 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8710400819088e430c8c550577e |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.