Triple

T10028807
Position Surface form Disambiguated ID Type / Status
Subject Gyeongbu Line E204798 entity
Predicate usedByService P1294 FINISHED
Object Mugunghwa-ho E190966 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: Mugunghwa-ho | Statement: [Gyeongbu Line, usedByService, Mugunghwa-ho]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mugunghwa-ho
Context triple: [Gyeongbu Line, usedByService, Mugunghwa-ho]
  • A. Mugunghwa-ho chosen
    Mugunghwa-ho is a class of South Korean intercity passenger trains operated by Korail, known for providing affordable, slower-speed service connecting major cities and regional areas.
  • B. Gukmun
    Gukmun is an old Korean term referring to the native Korean writing system that later came to be known as Joseongeul or Hangul.
  • C. Gwan-eum
    Gwan-eum is the Korean name for Guanyin, the bodhisattva of compassion widely revered in East Asian Buddhism.
  • D. Muye
    Muye was the site of an ancient Chinese battlefield where the Zhou forces decisively overthrew the Shang dynasty.
  • E. Sinseongbong
    Sinseongbong is a prominent mountain peak located within the Gyeryongsan mountain range in South Korea.
  • 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_69ca834d77188190ad645e33e8ca3200 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cdcde51c408190afb34010b1707014 completed April 2, 2026, 2:01 a.m.
NED1 Entity disambiguation (via context triple) batch_69d282351ebc8190b22bf3964823b0ee completed April 5, 2026, 3:39 p.m.
Created at: March 30, 2026, 8:54 p.m.