Triple

T8980895
Position Surface form Disambiguated ID Type / Status
Subject 금정구 E214521 entity
Predicate locatedIn P40 FINISHED
Object 부산광역시 E4279 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: 부산광역시 | Statement: [금정구, locatedIn, 부산광역시]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: 부산광역시
Context triple: [금정구, locatedIn, 부산광역시]
  • A. Busan metropolitan area
    The Busan metropolitan area is a major South Korean urban and economic hub centered on the port city of Busan, known for its extensive transportation links, coastal location, and role as a key gateway for international trade.
  • B. Incheon
    Incheon is a major port city in northwestern South Korea, known for its international airport and role as a key transportation and economic hub.
  • C. Busan chosen
    Busan is South Korea’s second-largest city and a major international port known for its bustling harbor, beaches, and coastal scenery.
  • D. Daegu
    Daegu is a major metropolitan city in southeastern South Korea known for its textile industry, electronics manufacturing, and cultural festivals.
  • E. Changwon
    Changwon is a major industrial and administrative city in South Gyeongsang Province, South Korea, known for its planned urban layout and role as a regional government and manufacturing hub.
  • 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_69ca839ea8b88190922c6a326ffcc0d3 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc67a76f748190a4abad5d53d58fa8 completed April 1, 2026, 12:32 a.m.
NED1 Entity disambiguation (via context triple) batch_69e4cbacad608190adddd91f13e4113b completed April 19, 2026, 12:33 p.m.
Created at: March 30, 2026, 7:03 p.m.