Triple

T5722479
Position Surface form Disambiguated ID Type / Status
Subject Battle of Zadwórze E126178 entity
Predicate location P40 FINISHED
Object Zadwórze E217541 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: Zadwórze | Statement: [Battle of Zadwórze, location, Zadwórze]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zadwórze
Context triple: [Battle of Zadwórze, location, Zadwórze]
  • A. Zadwórze chosen
    Zadwórze is a village in present-day western Ukraine known primarily as the site of the 1920 Battle of Zadwórze during the Polish–Soviet War.
  • B. Działdowo
    Działdowo is a town in northern Poland known for its historical significance and location within the Warmian-Masurian Voivodeship.
  • C. Zabierzów
    Zabierzów is a village in southern Poland that serves as the administrative seat of its rural commune near the city of Kraków.
  • D. Zułowo
    Zułowo is a village in present-day Lithuania best known as the birthplace of Józef Piłsudski, a key figure in Poland’s struggle for independence.
  • E. Dzierżoniów
    Dzierżoniów is a town in southwestern Poland known for its historical architecture and location in the Lower Silesian region.
  • 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_69c0082f723881908ce8bb13a0c0f8b7 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c024e6c444819089270b188e60cc67 completed March 22, 2026, 5:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7b89011a88190b498264ff99e7984 completed March 28, 2026, 11:16 a.m.
Created at: March 22, 2026, 3:46 p.m.