Triple

T7195266
Position Surface form Disambiguated ID Type / Status
Subject Honam region E168598 entity
Predicate hasMajorCity P316 FINISHED
Object Mokpo E613689 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: Mokpo | Statement: [Honam region, hasMajorCity, Mokpo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mokpo
Context triple: [Honam region, hasMajorCity, Mokpo]
  • A. Mokpo chosen
    Mokpo is a coastal city in South Jeolla Province, South Korea, known as a regional transportation hub and gateway to numerous nearby islands.
  • B. Gangjin
    Gangjin is a coastal county and town in South Jeolla Province, South Korea, known for its historic celadon pottery kilns and scenic rural landscapes.
  • C. Gwangyang
    Gwangyang is an industrial port city in South Korea known for its major steelworks complex and scenic coastal and mountainous landscapes.
  • D. Gunsan
    Gunsan is a coastal city in North Jeolla Province, South Korea, known for its port, industrial facilities, and longstanding association with nearby military air operations.
  • E. Yeosu
    Yeosu is a coastal city in South Jeolla Province, South Korea, known for its scenic archipelago, maritime industry, and role as host of the 2012 World Expo.
  • 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_69c68a5376748190bb500f03df86e93e completed March 27, 2026, 1:46 p.m.
NER Named-entity recognition batch_69c6e927709c81909edf6ee42fe7f833 completed March 27, 2026, 8:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69c845d90b48819081280063dcaafad7 completed March 28, 2026, 9:19 p.m.
Created at: March 27, 2026, 2:51 p.m.