Triple
T57049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Americans |
E1127
|
entity |
| Predicate | heritageFood |
P1016
|
FINISHED |
| Object | lefse |
—
|
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: lefse | Statement: [Norwegian Americans, heritageFood, lefse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageFood Context triple: [Norwegian Americans, heritageFood, lefse]
-
A.
traditionalCuisine
chosen
Indicates that an entity is associated with the customary or historically rooted style of cooking and food preparation characteristic of a particular culture, region, or community.
-
B.
hasHeritage
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
C.
feast
Indicates that an entity participates in or hosts a large, elaborate meal or celebration involving abundant food and communal dining.
-
D.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
E.
culturalTradition
Indicates a relationship where certain practices, beliefs, or customs are recognized as part of a shared cultural heritage passed down within a group or society.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b915c9881908c798f4dacb39f1d |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac6799c8190b508933acc0a4c7d |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.