Triple

T20748142
Position Surface form Disambiguated ID Type / Status
Subject Jinju-si E510642 entity
Predicate nearCity P350 FINISHED
Object Sacheon-si 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: Sacheon-si | Statement: [Jinju-si, nearCity, Sacheon-si]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sacheon-si
Context triple: [Jinju-si, nearCity, Sacheon-si]
  • A. Sacheon chosen
    Sacheon is a coastal city in South Gyeongsang Province, South Korea, known for its fishing industry, maritime transport, and aerospace manufacturing.
  • B. Hwaseong-si
    Hwaseong-si is a rapidly growing city in Gyeonggi Province, South Korea, known for its industrial complexes, coastal wetlands, and proximity to Seoul.
  • C. Yeoju
    Yeoju is a city in South Korea known for its rich historical heritage, including royal tombs and ceramics, and its scenic riverside landscapes.
  • D. Icheon
    Icheon is a South Korean city renowned for its traditional ceramics and hot spring resorts.
  • E. Kimhae-si
    Kimhae-si is an alternative romanized spelling of Gimhae, a city in South Gyeongsang Province, South Korea, known for its historical significance as the birthplace of the ancient Gaya confederacy.
  • 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_69e0b4c845e88190b4c5f3ae79291182 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c226fbf881909794eff3ee9e206b completed April 21, 2026, 12:17 a.m.
Created at: April 16, 2026, 12:33 p.m.