Triple

T15427507
Position Surface form Disambiguated ID Type / Status
Subject Segyo-dong E369549 entity
Predicate locatedIn P40 FINISHED
Object Sudogwon E227776 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: Sudogwon | Statement: [Segyo-dong, locatedIn, Sudogwon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sudogwon
Context triple: [Segyo-dong, locatedIn, 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. Wiryeseong
    Wiryeseong was the first capital city of the ancient Korean kingdom of Baekje, located in the Han River basin near present-day Seoul.
  • E. Hongje-dong
    Hongje-dong is a neighborhood in western Seoul, South Korea, known as a residential and commercial area within Seodaemun 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_69d85a1849f48190bf898068b2806fae completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ec31f4881908b26ff7c381d7bc9 completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff1a8099448190be71f7b649c7e545 completed May 9, 2026, 11:29 a.m.
Created at: April 10, 2026, 3:20 a.m.