Triple
T22350012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insadong |
E552502
|
entity |
| Predicate | hasMainStreet |
P461
|
FINISHED |
| Object | Insadong-gil |
—
|
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: Insadong-gil | Statement: [Insadong, hasMainStreet, Insadong-gil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Insadong-gil Context triple: [Insadong, hasMainStreet, Insadong-gil]
-
A.
Insadong
Insadong is a popular neighborhood in central Seoul known for its traditional Korean culture, antique shops, tea houses, and art galleries.
-
B.
Singil-dong
Singil-dong is a neighborhood (dong) in Seoul, South Korea, located within the city's southwestern Yeongdeungpo District.
-
C.
Insa-dong
chosen
Insa-dong is a popular neighborhood in central Seoul known for its traditional Korean culture, antique shops, art galleries, and teahouses.
-
D.
Hongje-dong
Hongje-dong is a neighborhood in western Seoul, South Korea, known as a residential and commercial area within Seodaemun District.
-
E.
Yangjeong-dong
Yangjeong-dong is a neighborhood (dong) located within Busanjin District in the city of Busan, South Korea.
- 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.