Triple

T17085167
Position Surface form Disambiguated ID Type / Status
Subject Taebaek Mountains E414576 entity
Predicate contains P35 FINISHED
Object Taebaeksan E1250421 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: Taebaeksan | Statement: [Taebaek Mountains, contains, Taebaeksan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Taebaeksan
Context triple: [Taebaek Mountains, contains, Taebaeksan]
  • A. Gyeryongsan
    Gyeryongsan is a prominent mountain in central South Korea known for its scenic national park, rich biodiversity, and cultural sites including historic Buddhist temples.
  • B. Ok-dong
    Ok-dong is a neighborhood in Ulsan, South Korea, known for encompassing the large urban green space of Ulsan Grand Park.
  • C. Geumjeongsan
    Geumjeongsan is a prominent mountain in Busan, South Korea, known for its scenic hiking trails, historic fortress walls, and cultural sites.
  • D. Baegunsan
    Baegunsan is a mountain located in or near the city of Uiwang in South Korea, known for its hiking trails and natural scenery.
  • E. Mount Taebaeksan chosen
    Mount Taebaeksan is a prominent, sacred mountain in eastern South Korea, renowned for its scenic ridges, ancient temples, and popular hiking trails.
  • 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_69d886cef44c8190ba56c44b4e863e64 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e3dbe6d5288190bdaec41c642d52a2 completed April 18, 2026, 7:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a014140722481909f976e32597a873d completed May 11, 2026, 2:38 a.m.
Created at: April 10, 2026, 5:35 a.m.