Triple
T14640719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Almeida |
E343712
|
entity |
| Predicate | hasCulturalAssociation |
P958
|
FINISHED |
| Object | Portuguese diaspora |
—
|
NE GENERATED |
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.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Portuguese diaspora Context triple: [de Almeida, hasCulturalAssociation, Portuguese diaspora]
-
A.
Portuguese diaspora
chosen
The Portuguese diaspora comprises communities of people of Portuguese origin living outside Portugal, formed through centuries of migration driven by exploration, trade, labor, and economic opportunity across the globe.
-
B.
Portuguese people
Portuguese people are a Romance-speaking ethnic group native to Portugal, known for their maritime heritage, global diaspora, and cultural influence across former Portuguese colonies.
-
C.
Asian Portuguese
Asian Portuguese is the variety of the Portuguese language spoken in several Asian countries and territories, shaped by local linguistic influences and historical Portuguese presence in the region.
-
D.
Portuguese American
Portuguese Americans are U.S. residents and citizens of Portuguese ancestry, many with roots in regions like the Azores and Madeira, who maintain distinct cultural traditions while integrating into broader American society.
-
E.
Luso-African diaspora
The Luso-African diaspora comprises communities of African origin historically shaped by Portuguese colonialism and migration, blending African and Portuguese cultural, linguistic, and social influences across multiple continents.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:26 a.m.