Triple

T14886542
Position Surface form Disambiguated ID Type / Status
Subject Jongno District E350135 entity
Predicate contains P35 FINISHED
Object Seochon E544806 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: Seochon | Statement: [Jongno District, contains, Seochon]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Seochon
Context triple: [Jongno District, contains, Seochon]
  • A. Seochon chosen
    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.
  • B. Wiryeseong
    Wiryeseong was the first capital city of the ancient Korean kingdom of Baekje, located in the Han River basin near present-day Seoul.
  • C. Jeongjeon
    Jeongjeon is the principal ceremonial hall of Seoul’s Jongmyo Shrine, where ancestral tablets of Joseon Dynasty kings and queens are enshrined and Confucian rites are performed.
  • D. Cheongsapo
    Cheongsapo is a small coastal village in Busan, South Korea, known for its scenic lighthouses, seaside cafes, and ocean views.
  • E. Joseongeul
    Joseongeul is the native Korean alphabetic writing system, more commonly known today as Hangul.
  • 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_69d822ee4f408190b6ac3b2fa434f0df completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded5f5b1c88190815f3585770cb135 completed April 15, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe6b5d0a208190b2490c86b15a42db completed May 8, 2026, 11:01 p.m.
Created at: April 10, 2026, 1:56 a.m.