Triple
T22350086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samcheong-dong |
E552503
|
entity |
| Predicate | hangulName |
P17869
|
FINISHED |
| Object | 삼청동 |
—
|
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: 삼청동 | Statement: [Samcheong-dong, hangulName, 삼청동]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 삼청동 Context triple: [Samcheong-dong, hangulName, 삼청동]
-
A.
Samcheong-dong
chosen
Samcheong-dong is a picturesque neighborhood in central Seoul known for its traditional hanok houses, art galleries, cafes, and proximity to historic palaces.
-
B.
Samseong-dong
Samseong-dong is a prominent neighborhood in Seoul, South Korea, known for its upscale shopping, business centers, and major landmarks like COEX Mall.
-
C.
Sujeong-dong
Sujeong-dong is a neighborhood (dong) located within Dong-gu, one of the central districts of the port city of Busan, South Korea.
-
D.
Daecheong-dong
Daecheong-dong is a neighborhood in central Busan, South Korea, known for its urban setting within the city's Jung District.
-
E.
Samseon-dong
Samseon-dong is a neighborhood (dong) in northern Seoul, South Korea, known as a residential area within the city's Seongbuk District.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1579ad6708190ba4af97a02d0758d |
completed | April 29, 2026, 12:58 a.m. |
Created at: April 16, 2026, 8:43 p.m.