Triple
T4410813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jung |
E94848
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Korean-language surname |
C14177
|
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: Korean-language surname Context triple: [Jung, instanceOf, Korean-language surname]
-
A.
Korean given name
A Korean given name is a personal name, typically consisting of two syllables written in Hangul (and sometimes Hanja), chosen to convey specific meanings, virtues, or aspirations for the individual.
-
B.
East Asian surname
chosen
An East Asian surname is a family name originating from countries such as China, Japan, Korea, and neighboring regions, often carrying historical, linguistic, and cultural significance unique to those societies.
-
C.
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.
-
D.
Hebrew-language surname
A Hebrew-language surname is a family name derived from or adapted into the Hebrew language, often reflecting Hebrew words, biblical names, places, or cultural-historical origins within Jewish communities.
-
E.
Slovak-language surname
A Slovak-language surname is a family name originating from or adapted to the Slovak language, typically reflecting Slovak phonology, morphology, and cultural naming 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_69b34539638c8190abfea3eb29425210 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:29 p.m.