Triple
T20002302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manuel Rodrigues (Portuguese given name) |
E494363
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Portuguese-language masculine given name |
C41064
|
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-language masculine given name Context triple: [Manuel Rodrigues (Portuguese given name), instanceOf, Portuguese-language masculine given name]
-
A.
Portuguese-language given name
chosen
A Portuguese-language given name is a personal first name used primarily by Portuguese speakers, often reflecting Lusophone cultural, religious, or historical influences.
-
B.
English masculine given name
An English masculine given name is a personal first name traditionally used for boys and men in English-speaking cultures, often derived from historical, biblical, or linguistic roots specific to the English language.
-
C.
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.
-
D.
masculine given name
A masculine given name is a personal name traditionally assigned to individuals identified as male, often reflecting cultural, historical, or familial significance.
-
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.
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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:33 p.m.