Triple
T5687795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asian Portuguese |
E125354
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diasporic Portuguese variety |
C6019
|
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: diasporic Portuguese variety Context triple: [Asian Portuguese, instanceOf, diasporic Portuguese variety]
-
A.
variety of Portuguese language
A variety of Portuguese language is a regional or social form of Portuguese characterized by distinct phonological, lexical, and grammatical features shared by a specific speech community.
-
B.
variety of Portuguese
chosen
A variety of Portuguese is a distinct form of the Portuguese language characterized by specific phonological, lexical, syntactic, and pragmatic features associated with a particular geographic region, social group, or communicative context.
-
C.
Portuguese-based creole
A Portuguese-based creole is a stable, fully developed language that arose from prolonged contact between Portuguese and one or more other languages, incorporating Portuguese-derived vocabulary within a distinct grammatical and phonological system.
-
D.
Portuguese language orthographic norm
The Portuguese language orthographic norm is the standardized set of spelling, accentuation, and hyphenation rules that regulate how Portuguese is correctly written across different countries and contexts.
-
E.
language of Portugal
The language of Portugal is European Portuguese, a Romance language derived from Latin and characterized by its distinct phonology, vocabulary, and grammar within the Lusophone world.
- F. None of above.
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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:44 p.m.