Triple

T14970758
Position Surface form Disambiguated ID Type / Status
Subject Doksan-dong E373309 entity
Predicate hasStandardRomanization P23170 FINISHED
Object Doksan-dong E373309 NE FINISHED

How this triple was built (3 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: Doksan-dong | Statement: [Doksan-dong, hasStandardRomanization, Doksan-dong]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Doksan-dong
Context triple: [Doksan-dong, hasStandardRomanization, Doksan-dong]
  • A. Doksan-dong chosen
    Doksan-dong is a neighborhood (dong) within the city of Osan in Gyeonggi Province, South Korea.
  • B. Dangsan-dong
    Dangsan-dong is a neighborhood in western Seoul, South Korea, known for its residential areas, commercial facilities, and convenient access via major subway lines.
  • C. Seo-dong
    Seo-dong is a neighborhood within Busan’s Geumjeong District in South Korea, known primarily as a residential area with local commerce and community facilities.
  • D. Yangsan-dong
    Yangsan-dong is a neighborhood (dong) within the city of Osan in Gyeonggi Province, South Korea.
  • E. Danggam-dong
    Danggam-dong is a neighborhood (dong) within Busanjin District in Busan, South Korea, known primarily as a residential and commercial urban area.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStandardRomanization
Context triple: [Doksan-dong, hasStandardRomanization, Doksan-dong]
  • A. hasRomanizationStandard chosen
    Indicates that an entity’s romanized form follows a specified romanization standard or system.
  • B. hasRomanizationOf
    Indicates that one entity is a romanized representation (written in the Latin alphabet) of the other entity’s original script form.
  • C. hasHakkaRomanization
    Indicates that an entity is associated with a specific representation of its name or term in Hakka Romanization.
  • D. hasMacronRomanization
    Indicates that an entity is associated with a Romanized form of text that uses macrons to mark long vowels.
  • E. hasRomanizationContrast
    Indicates that there is a meaningful difference between two or more romanized representations of the same original form.
  • F. None of above.

Provenance (4 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_69d85ccbbcd48190acb56e7cf104d8ad completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded6e59a7c8190a1634a706ea68fda completed April 15, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0025e9b00c81908cb5f305c894363f completed May 10, 2026, 6:30 a.m.
PD Predicate disambiguation batch_69de9a5d995881909e33658f5aea5582 completed April 14, 2026, 7:49 p.m.
Created at: April 10, 2026, 2:49 a.m.