Triple

T13265362
Position Surface form Disambiguated ID Type / Status
Subject Yeonsan-dong E315908 entity
Predicate district P2709 FINISHED
Object Yeonje-gu E36486 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: Yeonje-gu | Statement: [Yeonsan-dong, district, Yeonje-gu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Yeonje-gu
Context triple: [Yeonsan-dong, district, Yeonje-gu]
  • A. Yeonsu-gu
    Yeonsu-gu is an administrative district of Incheon, South Korea, known for its coastal location, modern residential areas, and proximity to the Songdo International Business District.
  • B. Suyeong-gu
    Suyeong-gu is a coastal district in the city of Busan, South Korea, known for its urban neighborhoods and proximity to popular beaches.
  • C. Gangseo-gu
    Gangseo-gu is a western coastal district of Busan, South Korea, known for its industrial complexes, logistics hubs, and proximity to Gimhae International Airport.
  • D. Seongbuk-gu
    Seongbuk-gu is a district in northern Seoul, South Korea, known for its residential neighborhoods, cultural sites, and several major universities.
  • E. Yeonje District chosen
    Yeonje District is an urban administrative district located in the central area of Busan, South Korea, known for its residential neighborhoods and transportation links.
  • 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_69d806b1d9ac8190852c5571d5bd5f0f completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d9901c65048190bd8b3c4872f22520 completed April 11, 2026, 12:04 a.m.
NED1 Entity disambiguation (via context triple) batch_69fd19226eb881908f76134a04e72548 completed May 7, 2026, 10:58 p.m.
Created at: April 9, 2026, 9:25 p.m.