Triple

T20476902
Position Surface form Disambiguated ID Type / Status
Subject Ungjin E502339 entity
Predicate predecessorCapital P3417 FINISHED
Object Wiryeseong 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: Wiryeseong | Statement: [Ungjin, predecessorCapital, Wiryeseong]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wiryeseong
Context triple: [Ungjin, predecessorCapital, Wiryeseong]
  • A. Wiryeseong chosen
    Wiryeseong was the first capital city of the ancient Korean kingdom of Baekje, located in the Han River basin near present-day Seoul.
  • B. Dongjum
    Dongjum is a small village in the province of Friesland in the northern Netherlands, known for its rural character and traditional Frisian landscape.
  • C. 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.
  • D. Sinseongbong
    Sinseongbong is a prominent mountain peak located within the Gyeryongsan mountain range in South Korea.
  • E. Donggureung
    Donggureung is a large royal burial complex in Guri, South Korea, containing multiple tombs of Joseon Dynasty kings and queens and recognized as part of a UNESCO World Heritage site.
  • 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_69e0b4af32848190aea80682b44d5d6e completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6996584648190a1a6dfcb57782b7f completed April 20, 2026, 9:23 p.m.
Created at: April 16, 2026, 11:34 a.m.