Triple

T2795327
Position Surface form Disambiguated ID Type / Status
Subject Battle of Pyongyang E53022 entity
Predicate hasLocation P40 FINISHED
Object Pyongyang E24920 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: Pyongyang | Statement: [Battle of Pyongyang, hasLocation, Pyongyang]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pyongyang
Context triple: [Battle of Pyongyang, hasLocation, Pyongyang]
  • A. Pyongyang chosen
    Pyongyang is the capital and largest city of North Korea, serving as its political, economic, and cultural center.
  • B. Sinuiju, Korea
    Sinuiju, Korea is a North Korean city on the Yalu River bordering China, known as an important industrial and transportation hub.
  • C. Seoul
    Seoul is the capital and largest metropolis of South Korea, known as a major global center for technology, culture, and finance.
  • D. Gwangju
    Gwangju is a major metropolitan city in southwestern South Korea known for its rich cultural heritage and pivotal role in the country’s pro-democracy movement.
  • E. Neryungri
    Neryungri is a major coal-mining and industrial city in southeastern Siberia, Russia, known as one of the key urban centers of the Sakha Republic (Yakutia).
  • 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_69ab495a90788190941b6917e1eca3a6 completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abddef754081908e6218dc2208e0fd completed March 7, 2026, 8:12 a.m.
NED1 Entity disambiguation (via context triple) batch_69afce9069f481908c4a3e8814caf590 completed March 10, 2026, 7:56 a.m.
Created at: March 6, 2026, 9:58 p.m.