Triple

T14089000
Position Surface form Disambiguated ID Type / Status
Subject Jung District, Seoul E339072 entity
Predicate contains P35 FINISHED
Object Namsan Seoul Tower E532617 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: Namsan Seoul Tower | Statement: [Jung District, Seoul, contains, Namsan Seoul Tower]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Namsan Seoul Tower
Context triple: [Jung District, Seoul, contains, Namsan Seoul Tower]
  • A. N Seoul Tower chosen
    N Seoul Tower is a prominent communication and observation tower on Namsan Mountain that serves as one of Seoul’s most recognizable cityscape landmarks and tourist attractions.
  • B. Kyobo Tower, Seoul
    Kyobo Tower in Seoul is a prominent modern office and commercial building best known as a landmark work of Swiss architect Mario Botta.
  • C. Busan Tower
    Busan Tower is a prominent observation tower in Busan, South Korea, offering panoramic views of the city and its harbor.
  • D. Samseongsan
    Samseongsan is a mountain in South Korea known for its hiking trails and views over the Anyang and southern Seoul metropolitan area.
  • E. Posco Tower Seoul
    Posco Tower Seoul is a prominent skyscraper and corporate office building in Seoul, South Korea, serving as a major landmark and business hub in the city.
  • 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_69d81c687b0c819087fd9ed4198403f8 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de5ee1ce88819091c983286289337e completed April 14, 2026, 3:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd0a5c9948190805c2e687c8809ff completed May 7, 2026, 5:49 p.m.
Created at: April 9, 2026, 10:21 p.m.