Triple
T34383297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ban family |
E882493
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | South Korean family |
C37930
|
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: South Korean family Context triple: [Ban family, instanceOf, South Korean family]
-
A.
South Korean business family
chosen
A South Korean business family is a kinship-based group that owns, controls, or significantly influences one or more enterprises in South Korea, often blending familial authority with corporate governance and social status.
-
B.
Korean-American
A Korean-American is an individual of Korean heritage who lives in or identifies with the United States, often blending elements of Korean and American cultures in their identity and daily life.
-
C.
Filipino family
A Filipino family is a close-knit, multigenerational household bound by strong kinship ties, deep respect for elders, shared responsibilities, and a culture of mutual support and togetherness.
-
D.
Korean clan
A Korean clan is a traditional kinship group sharing a common surname and ancestral origin, often traced to a specific founding ancestor and ancestral seat (bon-gwan), that structures lineage, identity, and social relations in Korean society.
-
E.
South Korean person
A South Korean person is an individual who holds South Korean nationality or identity, typically associated with the culture, language, and society of the Republic of Korea.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:59 a.m.