Triple

T17017859
Position Surface form Disambiguated ID Type / Status
Subject Yeongdeungpo-gu Office E412867 entity
Predicate hasOfficialName P66 FINISHED
Object 영등포구청 E412867 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: [Yeongdeungpo-gu Office, hasOfficialName, 영등포구청]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: 영등포구청
Context triple: [Yeongdeungpo-gu Office, hasOfficialName, 영등포구청]
  • A. Yeongdeungpo-gu Office chosen
    Yeongdeungpo-gu Office is the local district government administration for Yeongdeungpo-gu in Seoul, South Korea, overseeing public services, urban management, and community affairs.
  • B. 연제구
    연제구는 대한민국 부산광역시 중앙부에 위치한 행정구로, 주거·상업·행정 기능이 조화를 이루는 도심 지역이다.
  • C. Jongno-gu Office
    Jongno-gu Office is the main local government building and administrative headquarters serving the Jongno District in central Seoul, South Korea.
  • D. Seodaemun-gu Office
    Seodaemun-gu Office is the local district government office responsible for administering public services and municipal affairs in Seoul’s Seodaemun District.
  • E. Seongbuk-gu Office
    Seongbuk-gu Office is the main local government building and administrative headquarters serving Seoul’s Seongbuk District.
  • 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_69d886cc4170819093deddc7b8b4b6a7 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3d480a58c8190a3912d26debb4311 completed April 18, 2026, 6:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a011b4d6cb881909b64b4368fd97fa9 completed May 10, 2026, 11:57 p.m.
Created at: April 10, 2026, 5:33 a.m.