Triple

T21257859
Position Surface form Disambiguated ID Type / Status
Subject Namgang River E523915 entity
Predicate associatedWith P37 FINISHED
Object Jinjuseong 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: Jinjuseong | Statement: [Namgang River, associatedWith, Jinjuseong]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jinjuseong
Context triple: [Namgang River, associatedWith, Jinjuseong]
  • A. Jinjuseong chosen
    Jinjuseong is a historic fortress in Jinju, South Korea, renowned for its role in the Imjin War and its well-preserved traditional architecture.
  • 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. Sinseongbong
    Sinseongbong is a prominent mountain peak located within the Gyeryongsan mountain range in South Korea.
  • D. Gungnae-seong
    Gungnae-seong was the fortified capital city of the ancient Korean kingdom of Goguryeo, serving as a key political and military center.
  • E. Yeongneung
    Yeongneung is a royal tomb complex in Yeoju, South Korea, that houses the burial site of King Sejong the Great and is part of the UNESCO-listed Royal Tombs of the Joseon Dynasty.
  • 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_69e0b5146c108190adc9adb73e90abff completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e735e2f1d48190b566ab4d736fdbc4 completed April 21, 2026, 8:31 a.m.
Created at: April 16, 2026, 3:58 p.m.