Triple

T19768147
Position Surface form Disambiguated ID Type / Status
Subject Donggureung E474811 entity
Predicate contains P35 FINISHED
Object Mongneung 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: Mongneung | Statement: [Donggureung, contains, Mongneung]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mongneung
Context triple: [Donggureung, contains, Mongneung]
  • A. Myeongneung chosen
    Myeongneung is one of the royal burial sites from Korea’s Joseon Dynasty, forming part of the UNESCO-listed Royal Tombs complex.
  • B. Minyong
    Minyong is a subgroup of the Adi people, an indigenous community of Arunachal Pradesh in Northeast India known for its distinct language and cultural traditions.
  • C. Bokpyin
    Bokpyin is a coastal town in southern Myanmar known for its location near the Andaman Sea and its role in regional fishing and trade.
  • D. Geumho-gang
    Geumho-gang is a river in South Korea that flows through North Gyeongsang Province and Daegu before joining the Nakdong River.
  • E. Odaesan
    Odaesan is a prominent mountain in South Korea known for its scenic national park, rich biodiversity, and important Buddhist temples such as Woljeongsa.
  • 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_69d8e51a43a08190956bc6df13c91a77 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65358fc3c8190867fea2a2c4e7594 completed April 20, 2026, 4:24 p.m.
Created at: April 10, 2026, 1:48 p.m.