Triple
T14886554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jongno District |
E350135
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Pyeongchang-dong |
E566792
|
NE FINISHED |
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: Pyeongchang-dong | Statement: [Jongno District, contains, Pyeongchang-dong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyeongchang-dong Context triple: [Jongno District, contains, Pyeongchang-dong]
-
A.
Pyeongchang-dong
chosen
Pyeongchang-dong is a residential neighborhood in northern Seoul, South Korea, known for its hilly terrain, upscale homes, and numerous art galleries and cultural institutions.
-
B.
Changcheon-dong
Changcheon-dong is a neighborhood in Seodaemun-gu, Seoul, South Korea, known for its proximity to the bustling Sinchon area and its mix of residential and commercial spaces.
-
C.
Yangpyeong-dong
Yangpyeong-dong is a neighborhood (dong) in Seoul, South Korea, located within the city's southwestern Yeongdeungpo District.
-
D.
Sinchang-dong
Sinchang-dong is a neighborhood (dong) located within Jung District in the coastal city of Busan, South Korea.
-
E.
Jungang-dong
Jungang-dong is a neighborhood in central Busan, South Korea, known for its urban commercial areas and proximity to major downtown facilities.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5f5b1c88190815f3585770cb135 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffdbb7b1e48190b55c40e0cb837446 |
completed | May 10, 2026, 1:13 a.m. |
Created at: April 10, 2026, 1:56 a.m.