Triple
T14886564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jongno District |
E350135
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Samil-dong |
E577273
|
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: Samil-dong | Statement: [Jongno District, contains, Samil-dong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Samil-dong Context triple: [Jongno District, contains, Samil-dong]
-
A.
Samil-dong
chosen
Samil-dong is a neighborhood (dong) located within Jongno-gu in central Seoul, South Korea, known for its mix of traditional and modern urban spaces.
-
B.
Sasang-dong
Sasang-dong is a neighborhood in Busan, South Korea, known as an urban residential and commercial area within the city's Sasang District.
-
C.
Bumseong-dong
Bumseong-dong is a neighborhood (dong) located within Pusanjin District in Busan, South Korea.
-
D.
Sogyeok-dong
Sogyeok-dong is a neighborhood in central Seoul, South Korea, known for its traditional Korean houses (hanok), art galleries, and proximity to historic palaces.
-
E.
Umyeon-dong
Umyeon-dong is a neighborhood in southern Seoul, South Korea, known for its residential areas near Umyeon Mountain and its location within the affluent Gangnam region.
- 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_6a001f79c6ac81909935dace3dcc8bea |
completed | May 10, 2026, 6:02 a.m. |
Created at: April 10, 2026, 1:56 a.m.