Triple

T3747382
Position Surface form Disambiguated ID Type / Status
Subject Republic of Korea Air Force E81240 entity
Predicate headquartersLocation P62 FINISHED
Object Seoul E19209 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: Seoul | Statement: [Republic of Korea Air Force, headquartersLocation, Seoul]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Seoul
Context triple: [Republic of Korea Air Force, headquartersLocation, Seoul]
  • A. Seoul chosen
    Seoul is the capital and largest metropolis of South Korea, known as a major global center for technology, culture, and finance.
  • B. Incheon
    Incheon is a major port city in northwestern South Korea, known for its international airport and role as a key transportation and economic hub.
  • C. Daejeon
    Daejeon is a major city in central South Korea known as a hub for science, technology, and research institutions.
  • D. Daegu
    Daegu is a major metropolitan city in southeastern South Korea known for its textile industry, electronics manufacturing, and cultural festivals.
  • E. 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.
  • 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_69ad8b19b7b08190a6188804e99c53e9 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcb6ac5ac8190934ec1a6c887a8f5 completed March 8, 2026, 7:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4db23ff3c81908d19295a7ce4a39c completed March 14, 2026, 3:51 a.m.
Created at: March 8, 2026, 3:35 p.m.