Triple

T6566476
Position Surface form Disambiguated ID Type / Status
Subject Chungcheong region E153918 entity
Predicate hasMajorCity P316 FINISHED
Object Asan E215809 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: Asan | Statement: [Chungcheong region, hasMajorCity, Asan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Asan
Context triple: [Chungcheong region, hasMajorCity, Asan]
  • A. Asan chosen
    Asan is a city in South Korea known for its hot springs, historical sites, and growing role as an industrial and educational center.
  • B. Hasana
    Hasana is a small town in Egypt’s North Sinai Governorate, situated in the Sinai Peninsula.
  • C. Akhasheni
    Akhasheni is a Georgian red wine appellation from the Kakheti region, known for its naturally semi-sweet wines made primarily from Saperavi grapes.
  • D. Asmal
    Asmal is a surname most notably associated with Kader Asmal, a prominent South African anti-apartheid activist, academic, and government minister.
  • E. Rushan
    Rushan is a county-level coastal city in eastern Shandong Province, China, known for its fishing industry, beaches, and marine-based economy.
  • 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_69c6880cb35881909b763eb0125236b9 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ae5381e88190b44dc4440efdd8ae completed March 27, 2026, 4:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6d564cb908190bb8885e6c8d8abac completed March 27, 2026, 7:07 p.m.
Created at: March 27, 2026, 1:52 p.m.