Triple

T18526178
Position Surface form Disambiguated ID Type / Status
Subject Bandung Regency E452722 entity
Predicate contains P35 FINISHED
Object Soreang NE NERFINISHED

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: Soreang | Statement: [Bandung Regency, contains, Soreang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Soreang
Context triple: [Bandung Regency, contains, Soreang]
  • A. Soreang chosen
    Soreang is a suburban district and the administrative center of Bandung Regency in West Java, Indonesia, situated within the greater Bandung metropolitan area.
  • B. Sokcho
    Sokcho is a coastal city in northeastern South Korea known for its beaches, seafood, and proximity to Seoraksan National Park.
  • C. Taebong
    Taebong was a short-lived Korean kingdom of the early 10th century that emerged during the Later Three Kingdoms period before being absorbed by Goryeo.
  • D. Seogwipo
    Seogwipo is a coastal city on South Korea’s Jeju Island known for its waterfalls, volcanic landscapes, and popular tourist attractions.
  • E. Nakchhong
    Nakchhong is a traditional ritual specialist and religious officiant within the Kirat Mundhum indigenous belief system.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8d387b5548190aa030dad2cb4947e completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e53392618c8190b44de46b80ee6a6d completed April 19, 2026, 7:57 p.m.
Created at: April 10, 2026, 11:37 a.m.