Triple

T7026863
Position Surface form Disambiguated ID Type / Status
Subject South Jeolla region E162969 entity
Predicate hasPortCity P2745 FINISHED
Object Gwangyang E659732 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: Gwangyang | Statement: [South Jeolla region, hasPortCity, Gwangyang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gwangyang
Context triple: [South Jeolla region, hasPortCity, Gwangyang]
  • A. Gwangyang chosen
    Gwangyang is an industrial port city in South Korea known for its major steelworks complex and scenic coastal and mountainous landscapes.
  • 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. Mokpo
    Mokpo is a coastal city in South Jeolla Province, South Korea, known as a regional transportation hub and gateway to numerous nearby islands.
  • D. Dangjin
    Dangjin is a coastal city in South Chungcheong Province, South Korea, known for its heavy industry, steel production, and port facilities on the Yellow Sea.
  • E. 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.
  • 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_69c6885b26248190a857541e3d10e299 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6e1fd6ab48190865271e16e8ff669 completed March 27, 2026, 8:01 p.m.
NED1 Entity disambiguation (via context triple) batch_69c83423e5008190881a7e956c716687 completed March 28, 2026, 8:03 p.m.
Created at: March 27, 2026, 2:35 p.m.