Triple

T22350107
Position Surface form Disambiguated ID Type / Status
Subject Jongno 5-ga E552504 entity
Predicate region P40 FINISHED
Object Sudogwon 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: Sudogwon | Statement: [Jongno 5-ga, region, Sudogwon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sudogwon
Context triple: [Jongno 5-ga, region, Sudogwon]
  • A. Sudogwon chosen
    Sudogwon is the Seoul Capital Area of South Korea, encompassing Seoul, Incheon, and surrounding Gyeonggi Province as the country’s largest and most populous metropolitan region.
  • B. Gwangalli
    Gwangalli is a coastal neighborhood in Busan, South Korea, best known for its sandy beach, vibrant nightlife, and scenic views of the nearby Gwangan Bridge.
  • C. Seochon
    Seochon is a historic neighborhood in central Seoul known for its traditional hanok houses, narrow alleyways, and vibrant mix of old Korean culture and modern cafes and galleries.
  • D. Dongmyeong
    Dongmyeong is another name for Jumong, the legendary founder and first king of the ancient Korean kingdom of Goguryeo.
  • E. Danggogae
    Danggogae is a station in northeastern Seoul that serves as the northern terminus of Seoul Subway Line 4.
  • 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.