Triple
T20537081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongsan-gu |
E504227
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Itaewon-dong |
—
|
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: Itaewon-dong | Statement: [Yongsan-gu, contains, Itaewon-dong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Itaewon-dong Context triple: [Yongsan-gu, contains, Itaewon-dong]
-
A.
Itaewon
chosen
Itaewon is a vibrant multicultural district in Seoul known for its international cuisine, nightlife, and diverse expatriate community.
-
B.
Gangdong-dong
Gangdong-dong is a neighborhood in Busan, South Korea, serving as the central administrative hub of the city's Gangseo District.
-
C.
Hongje-dong
Hongje-dong is a neighborhood in western Seoul, South Korea, known as a residential and commercial area within Seodaemun District.
-
D.
Gangnam-daero
Gangnam-daero is a major thoroughfare in Seoul’s Gangnam district, known for its dense commercial development, heavy traffic, and role as a central hub of business and nightlife.
-
E.
Cheongdam-dong
Cheongdam-dong is an affluent neighborhood in Seoul known for its luxury boutiques, high-end residences, and trendy cafes and galleries.
- 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_69e0b4b476648190bc6019622ae54d3c |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a28f2f1081908f656d790ff182ff |
completed | April 20, 2026, 10:02 p.m. |
Created at: April 16, 2026, 11:37 a.m.