Triple
T13260909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koreatown |
E315789
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Korean-American neighborhood |
C3470
|
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-American neighborhood Context triple: [Koreatown, instanceOf, Korean-American neighborhood]
-
A.
Filipino-American cultural district
A Filipino-American cultural district is a designated urban area that concentrates Filipino-owned businesses, community institutions, public art, and cultural events to celebrate, preserve, and promote Filipino-American heritage and identity.
-
B.
Koreatown
chosen
Koreatown is an urban neighborhood characterized by a high concentration of Korean residents, businesses, and cultural institutions that serve as a hub for Korean culture and community life outside of Korea.
-
C.
Mexican-American neighborhood
A Mexican-American neighborhood is a residential area where a significant portion of the population is of Mexican descent, shaping the local culture, businesses, language use, and community life.
-
D.
Autonomous district of South Korea
An autonomous district of South Korea is a self-governing municipal subdivision within a metropolitan city or special city that has its own local government and administrative authority over local affairs.
-
E.
Irish-American neighborhood
An Irish-American neighborhood is a residential area where a significant concentration of people of Irish descent live, maintaining distinct cultural traditions, social institutions, and community networks rooted in Irish heritage within the broader American context.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:25 p.m.