Triple

T18037479
Position Surface form Disambiguated ID Type / Status
Subject Gmina Bielawy E431548 entity
Predicate containsSettlement P847 FINISHED
Object Borów 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: Borów | Statement: [Gmina Bielawy, containsSettlement, Borów]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Borów
Context triple: [Gmina Bielawy, containsSettlement, Borów]
  • A. Borów chosen
    Borów is a small settlement located within the administrative district of Gmina Bukowno in southern Poland.
  • B. Bolków
    Bolków is a small historic town in southwestern Poland, best known for its medieval castle and annual rock music festival.
  • C. Budzów
    Budzów is a village in southern Poland located in the Lesser Poland Voivodeship within the administrative district of Sucha County (powiat suski).
  • D. Rakowice
    Rakowice is a historic district in Kraków, Poland, known for its large military cemetery and proximity to the city center.
  • E. Sobieszów
    Sobieszów is a district of the city of Jelenia Góra in southwestern Poland, known for its proximity to the Karkonosze Mountains and the historic Chojnik Castle.
  • 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_69d8b9050fb48190890155145deb0a66 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4be3bc3208190a6db569e79f06232 completed April 19, 2026, 11:36 a.m.
Created at: April 10, 2026, 10:25 a.m.