Triple

T20002836
Position Surface form Disambiguated ID Type / Status
Subject Yeongneung (Paju) E494377 entity
Predicate locatedIn P40 FINISHED
Object Paju 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: Paju | Statement: [Yeongneung (Paju), locatedIn, Paju]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paju
Context triple: [Yeongneung (Paju), locatedIn, Paju]
  • A. Paju chosen
    Paju is a city in South Korea near the Demilitarized Zone, known for its historical sites, cultural complexes, and role as a border hub with North Korea.
  • B. Sariwon
    Sariwon is a major city in southwestern North Korea known as an administrative, transportation, and agricultural center.
  • C. Balgüe
    Balgüe is a small rural village on Ometepe Island in Lake Nicaragua, known for its scenic setting near volcanic landscapes and eco-tourism lodges.
  • D. Mahwa
    Mahwa is a town located in the Dausa district of the Indian state of Rajasthan.
  • E. Soreang
    Soreang is a suburban district and the administrative center of Bandung Regency in West Java, Indonesia, situated within the greater Bandung metropolitan area.
  • 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_69da626b2d748190886981ea90c8b2ea completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e661a2e34481908a495cc5d077c41f completed April 20, 2026, 5:25 p.m.
Created at: April 11, 2026, 3:33 p.m.