Triple

T19089317
Position Surface form Disambiguated ID Type / Status
Subject Seoul Station E467238 entity
Predicate serves P98 FINISHED
Object Mugunghwa-ho 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: Mugunghwa-ho | Statement: [Seoul Station, serves, Mugunghwa-ho]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mugunghwa-ho
Context triple: [Seoul Station, serves, 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. Hwangje
    Hwangje is the Korean imperial title corresponding to the Chinese sovereign known as the Yellow Emperor (Huangdi).
  • C. Gugundhabe
    Gugundhabe is a Somali subclan within the larger Hawiye clan-family, traditionally associated with central and southern Somalia.
  • D. Hoeryong
    Hoeryong is a city in northeastern North Korea known for its location near the Chinese border and its association with the country's political prison camp system.
  • E. Gukmun
    Gukmun is an old Korean term referring to the native Korean writing system that later came to be known as Joseongeul or Hangul.
  • 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_69d8dd05ac4c8190b1967d8f97f3fb2f completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5e34981648190a89b006831846940 completed April 20, 2026, 8:26 a.m.
Created at: April 10, 2026, 12:04 p.m.