Triple

T15862554
Position Surface form Disambiguated ID Type / Status
Subject Kholm E384627 entity
Predicate modernName P1213 FINISHED
Object Chełm 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: Chełm | Statement: [Kholm, modernName, Chełm]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chełm
Context triple: [Kholm, modernName, Chełm]
  • A. Chełm chosen
    Chełm is a city in eastern Poland known for its historical significance, including its role in World War II-era political developments and its distinctive chalk tunnels and religious heritage.
  • B. Haczów
    Haczów is a village in southeastern Poland known for its historic wooden architecture and cultural heritage, including one of the oldest and largest Gothic wooden churches in Europe.
  • C. Ciechanów
    Ciechanów is a historic town in east-central Poland, known as a regional center of the Mazovian area with a medieval castle and long-standing cultural traditions.
  • D. Parczew
    Parczew is a small town in eastern Poland known for its historical roots and location within the Lublin region.
  • E. Czersk
    Czersk is a town in northern Poland known for its location in the Pomeranian Voivodeship and its historical ties to regional noble lineages.
  • 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_69d86da422088190aac39e32e6c68429 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1555c75688190aeae5bcf5bb92bb7 completed April 16, 2026, 9:32 p.m.
Created at: April 10, 2026, 4:50 a.m.