Triple

T9433801
Position Surface form Disambiguated ID Type / Status
Subject Gwangan-dong E227450 entity
Predicate romanization P2508 FINISHED
Object Gwangan-dong (RR) E227450 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: Gwangan-dong (RR) | Statement: [Gwangan-dong, romanization, Gwangan-dong (RR)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gwangan-dong (RR)
Context triple: [Gwangan-dong, romanization, Gwangan-dong (RR)]
  • A. Gwangan-dong chosen
    Gwangan-dong is a coastal neighborhood in Busan, South Korea, best known for Gwangalli Beach and its views of the illuminated Gwangan Bridge.
  • B. Gwancheol-dong
    Gwancheol-dong is a neighborhood in central Seoul, South Korea, known for its location within the historic Jongno district.
  • C. Donggwang-dong
    Donggwang-dong is a neighborhood (dong) located within Jung District in central Busan, South Korea, known for its urban setting and proximity to the city’s historic and commercial areas.
  • D. Guwol-dong
    Guwol-dong is a major neighborhood in Incheon, South Korea, known as the administrative and commercial center of Namdong District.
  • E. Gwaebeop-dong
    Gwaebeop-dong is a neighborhood in Busan, South Korea, known as an administrative subdivision of the city's Sasang 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_69ca8437a7ac81908651de48f2d2141d completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd7e62d53c81908055e0967e6cd54d completed April 1, 2026, 8:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1104514d481908d7cb9a87a01f1e2 completed April 4, 2026, 1:21 p.m.
Created at: March 30, 2026, 7:49 p.m.