Triple

T7601793
Position Surface form Disambiguated ID Type / Status
Subject Kulm E180000 entity
Predicate hasGermanName P1435 FINISHED
Object Kulm E180000 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: Kulm | Statement: [Kulm, hasGermanName, Kulm]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kulm
Context triple: [Kulm, hasGermanName, Kulm]
  • A. Kulm chosen
    Kulm, now known as Chełmno in Poland, is a historic town on the Vistula River notable for its medieval architecture and role in the history of Royal Prussia.
  • B. Krempna
    Krempna is a small village in southeastern Poland that serves as a gateway and service center for visitors to Magura National Park in the Low Beskid Mountains.
  • C. Kremmen
    Kremmen is a small town and municipality in the Oberhavel district of the German state of Brandenburg.
  • D. Koshice
    Košice is the second-largest city in Slovakia, known for its well-preserved medieval old town and status as an important cultural and economic center in the country.
  • E. Taborio
    Taborio is a village settlement located on the island of Nonouti in the Republic of Kiribati.
  • 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_69c69f3567008190ab01d2ca7b53584a completed March 27, 2026, 3:16 p.m.
NER Named-entity recognition batch_69c6f9f8e7848190b44d9c16b9c95d37 completed March 27, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69c86846192c81909154e6cf60b21157 completed March 28, 2026, 11:46 p.m.
Created at: March 27, 2026, 3:54 p.m.