Triple
T9009927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurelius |
E215441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Latin-language surname |
C12599
|
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: Latin-language surname Context triple: [Aurelius, instanceOf, Latin-language surname]
-
A.
Latin family name
chosen
A Latin family name is a hereditary surname of Latin origin, often derived from personal names, occupations, locations, or characteristic traits, used to identify and distinguish members of a family lineage.
-
B.
Spanish-language surname
A Spanish-language surname is a family name of Spanish origin or usage, often reflecting ancestry, geography, occupation, or personal characteristics within Spanish-speaking cultures.
-
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.
Hungarian-language surname
A Hungarian-language surname is a family name of Hungarian origin that typically follows Hungarian linguistic patterns and may reflect ancestry, occupation, geography, or personal characteristics within Hungarian culture.
-
E.
Polish-language surname
A Polish-language surname is a family name originating from the Polish language, often reflecting ancestry, occupation, geography, or personal characteristics within Polish cultural and linguistic traditions.
- 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_69ca83a2bf088190986ee7a8eb90407d |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:06 p.m.