Triple
T7559006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koreatown (Bloor between Bathurst and Christie) |
E178746
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Korean business district |
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 business district Context triple: [Koreatown (Bloor between Bathurst and Christie), instanceOf, Korean business district]
-
A.
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.
-
B.
special city in South Korea
A special city in South Korea is a top-level administrative division that functions as a city with the same status as a province, directly governed by the central government and typically encompassing a large urban area.
-
C.
city in South Korea
A city in South Korea is an urban administrative division governed by local authorities, characterized by concentrated population, infrastructure, and economic, cultural, and social activities within the Republic of Korea.
-
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.
gu of Incheon
A gu of Incheon is an administrative district-level division within the metropolitan city of Incheon, South Korea, responsible for local governance, public services, and community management in its designated urban area.
- 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:50 p.m.