Triple
T29049575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alentejo pork products |
E735229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portuguese regional specialty |
C54635
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Portuguese regional specialty Context triple: [Alentejo pork products, instanceOf, Portuguese regional specialty]
-
A.
Portuguese traditional drink
A Portuguese traditional drink is a culturally rooted beverage, often alcoholic, made using regional ingredients and methods that reflect Portugal’s culinary heritage and local customs.
-
B.
Portuguese cultural phenomenon
A Portuguese cultural phenomenon is a widely recognized and collectively experienced practice, trend, or expression that reflects and shapes Portugal’s social values, history, and national identity.
-
C.
Portuguese cultural practice
A Portuguese cultural practice is a traditional or contemporary social behavior, ritual, or custom rooted in Portugal’s history and values, expressed through everyday life, celebrations, arts, cuisine, or community interactions.
-
D.
region of Portugal
A region of Portugal is a geographically defined area within the country characterized by shared administrative boundaries, cultural traits, economic activities, and environmental features.
-
E.
Portuguese appellation
A Portuguese appellation is a legally defined and protected geographical indication used to designate wines or other agricultural products originating from specific regions of Portugal that meet established quality and production standards.
- F. None of above. chosen
Provenance (1 batch)
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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 10:07 a.m.