Triple
T14665945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinchon-dong |
E344372
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object |
Yeonhui-dong
Yeonhui-dong is a neighborhood in Seodaemun District, Seoul, known for its quiet residential character and proximity to major university and commercial areas like Sinchon.
|
E1127813
|
NE FINISHED |
How this triple was built (4 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: Yeonhui-dong | Statement: [Sinchon-dong, adjacentTo, Yeonhui-dong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yeonhui-dong Context triple: [Sinchon-dong, adjacentTo, Yeonhui-dong]
-
A.
Hoehyeon-dong
Hoehyeon-dong is a neighborhood in central Seoul, South Korea, known for its proximity to major commercial and historical areas such as Myeong-dong and Namdaemun Market.
-
B.
Yongho-dong
Yongho-dong is a neighborhood in Busan, South Korea, known as a coastal residential area within the city's southern region.
-
C.
Seongho-dong
Seongho-dong is a neighborhood (dong) within the city of Osan in Gyeonggi Province, South Korea.
-
D.
Yeonji-dong
Yeonji-dong is a neighborhood (dong) located within Pusanjin District in Busan, South Korea.
-
E.
Yeonsu-dong
Yeonsu-dong is a neighborhood within Incheon, South Korea, known as a residential and local commercial area of Yeonsu District.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Yeonhui-dong Triple: [Sinchon-dong, adjacentTo, Yeonhui-dong]
Generated description
Yeonhui-dong is a neighborhood in Seodaemun District, Seoul, known for its quiet residential character and proximity to major university and commercial areas like Sinchon.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Yeonhui-dong Target entity description: Yeonhui-dong is a neighborhood in Seodaemun District, Seoul, known for its quiet residential character and proximity to major university and commercial areas like Sinchon.
-
A.
Hoehyeon-dong
Hoehyeon-dong is a neighborhood in central Seoul, South Korea, known for its proximity to major commercial and historical areas such as Myeong-dong and Namdaemun Market.
-
B.
Yongho-dong
Yongho-dong is a neighborhood in Busan, South Korea, known as a coastal residential area within the city's southern region.
-
C.
Seongho-dong
Seongho-dong is a neighborhood (dong) within the city of Osan in Gyeonggi Province, South Korea.
-
D.
Yeonji-dong
Yeonji-dong is a neighborhood (dong) located within Pusanjin District in Busan, South Korea.
-
E.
Yeonsu-dong
Yeonsu-dong is a neighborhood within Incheon, South Korea, known as a residential and local commercial area of Yeonsu District.
- F. None of above. chosen
Provenance (5 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_69d822e283fc8190a0e4c235cf880052 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb54c69f8819080a37161deecfba8 |
completed | April 14, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe7e7772508190bee1eb310aa40372 |
completed | May 9, 2026, 12:23 a.m. |
| NEDg | Description generation | batch_69fe7f9ea5848190af5edd6d2d22c117 |
completed | May 9, 2026, 12:28 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fe7ff91dec8190aa9f0d42a8cd00e0 |
completed | May 9, 2026, 12:29 a.m. |
Created at: April 10, 2026, 1:27 a.m.