Triple

T11500844
Position Surface form Disambiguated ID Type / Status
Subject Warsaw Voivodeship (interwar) E272659 entity
Predicate containsAdministrativeTerritorialEntity P747 FINISHED
Object Łomża E940098 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: Łomża | Statement: [Warsaw Voivodeship (interwar), containsAdministrativeTerritorialEntity, Łomża]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Łomża
Context triple: [Warsaw Voivodeship (interwar), containsAdministrativeTerritorialEntity, Łomża]
  • A. Łomża chosen
    Łomża is a historic town in northeastern Poland known for its picturesque setting near the Narew River and its regional cultural significance.
  • B. Wołomin
    Wołomin is a town in east-central Poland that functions as a suburban community within the greater Warsaw metropolitan area.
  • C. Radom
    Radom is a city in central Poland known as an important regional industrial and cultural center.
  • D. Białogard
    Białogard is a historic town in northwestern Poland, located in the West Pomeranian Voivodeship on the Parsęta River.
  • E. Pułtusk
    Pułtusk is a historic town in east-central Poland, known for its medieval heritage and its role as the site of several significant battles, including during the Napoleonic Wars.
  • 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_69d6aae1b09881909ce2ded3fa0c14fa completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d85de3e9c881909d6c55334f7a832d completed April 10, 2026, 2:18 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff453c189c8190ac73204b7ac68dda completed May 9, 2026, 2:31 p.m.
Created at: April 8, 2026, 9:36 p.m.