Triple
T22640541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheongunhyoja-dong |
E558811
|
entity |
| Predicate | hasRomanizedName |
P2508
|
FINISHED |
| Object | Cheongunhyoja-dong (RR) |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Cheongunhyoja-dong (RR) | Statement: [Cheongunhyoja-dong, hasRomanizedName, Cheongunhyoja-dong (RR)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Cheongunhyoja-dong (RR) Context triple: [Cheongunhyoja-dong, hasRomanizedName, Cheongunhyoja-dong (RR)]
-
A.
Cheongunhyoja-dong
chosen
Cheongunhyoja-dong is a neighborhood in central Seoul, South Korea, known for its proximity to historic sites and government institutions within Jongno-gu.
-
B.
Yeonji-dong
Yeonji-dong is a neighborhood (dong) located within Pusanjin District in Busan, South Korea.
-
C.
Cheonghak-dong
Cheonghak-dong is a neighborhood within the city of Osan in Gyeonggi Province, South Korea.
-
D.
Cheonghak-dong
Cheonghak-dong is a neighborhood (dong) located within Dong-gu, one of the central districts of Busan, South Korea.
-
E.
Yeomchang-dong
Yeomchang-dong is a neighborhood in the Gangseo District of western Seoul, South Korea, known primarily as a residential area with convenient access to the Han River and central Seoul.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 batches)
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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f170116fe881908178cffef26e3ae7 |
completed | April 29, 2026, 2:42 a.m. |
Created at: April 17, 2026, 3:04 p.m.