Triple
T27136949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | -inho |
E681713
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portuguese diminutive suffix |
C52529
|
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 diminutive suffix Context triple: [-inho, instanceOf, Portuguese diminutive suffix]
-
A.
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.
-
B.
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.
-
C.
Portuguese-language given name
A Portuguese-language given name is a personal first name used primarily by Portuguese speakers, often reflecting Lusophone cultural, religious, or historical influences.
-
D.
Portuguese-language surname
A Portuguese-language surname is a family name originating from Portuguese linguistic and cultural traditions, typically used to identify lineage, heritage, or geographic roots within Portuguese-speaking communities.
-
E.
Beja language
The Beja language is an Afroasiatic Cushitic language spoken primarily by the Beja people across parts of Sudan, Egypt, and Eritrea, notable for its conservative linguistic features and limited written tradition.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:07 a.m.