Triple

T12158303
Position Surface form Disambiguated ID Type / Status
Subject Kangseo-gu E289635 entity
Predicate hasOfficialName P66 FINISHED
Object Gangseo-gu E692405 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: Gangseo-gu | Statement: [Kangseo-gu, hasOfficialName, Gangseo-gu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gangseo-gu
Context triple: [Kangseo-gu, hasOfficialName, Gangseo-gu]
  • A. Gangseo-gu chosen
    Gangseo-gu is a western coastal district of Busan, South Korea, known for its industrial complexes, logistics hubs, and proximity to Gimhae International Airport.
  • B. Seongbuk-gu
    Seongbuk-gu is a district in northern Seoul, South Korea, known for its residential neighborhoods, cultural sites, and several major universities.
  • C. 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.
  • D. 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.
  • E. Jung-gu
    Jung-gu is a central district of the metropolitan city of Daejeon in South Korea, known for its mix of commercial, residential, and administrative areas.
  • 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_69d6ab4c6710819097a9d228382dde43 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915c277e481908351bf4e664dda42 completed April 10, 2026, 3:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69f716afa8008190b4c518dd6004d87a completed May 3, 2026, 9:34 a.m.
Created at: April 8, 2026, 9:50 p.m.