Triple
T14886555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jongno District |
E350135
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Sajik-dong |
E563258
|
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: Sajik-dong | Statement: [Jongno District, contains, Sajik-dong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sajik-dong Context triple: [Jongno District, contains, Sajik-dong]
-
A.
Sajik-dong
chosen
Sajik-dong is a neighborhood in central Seoul, South Korea, known for its proximity to historic sites such as Gyeongbokgung Palace and major government institutions.
-
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.
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.
-
D.
Jangwi-dong
Jangwi-dong is a neighborhood in northern Seoul, South Korea, known as a residential area within the city's Seongbuk District.
-
E.
Jangjeon-dong
Jangjeon-dong is a neighborhood in Busan, South Korea, known as an administrative and residential center within Geumjeong District.
- 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_69ffe46436048190b79d1d18a179617b |
completed | May 10, 2026, 1:50 a.m. |
Created at: April 10, 2026, 1:56 a.m.