Triple

T18235038
Position Surface form Disambiguated ID Type / Status
Subject Rębiechowo E436650 entity
Predicate hasPolishName P15778 FINISHED
Object Rębiechowo 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: Rębiechowo | Statement: [Rębiechowo, hasPolishName, Rębiechowo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rębiechowo
Context triple: [Rębiechowo, hasPolishName, Rębiechowo]
  • A. Rębiechowo chosen
    Rębiechowo is a village in northern Poland, near Gdańsk, best known for hosting the Gdańsk Lech Wałęsa Airport.
  • B. Rakowice
    Rakowice is a historic district in Kraków, Poland, known for its large military cemetery and proximity to the city center.
  • C. Władysławowo
    Władysławowo is a Polish seaside town and popular tourist resort on the Baltic coast, known for its beaches and fishing port.
  • D. Krobielowice
    Krobielowice is a village in southwestern Poland, historically known by its German name Krieblowitz, noted for its manor house and rural setting near Wrocław.
  • E. Wojnowo
    Wojnowo is a village in western Poland that was formerly known by its German name Reckenwalde.
  • 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_69d8b91104e08190a8241f7d260a5162 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4f4b5ce608190b6fba518256607da completed April 19, 2026, 3:28 p.m.
Created at: April 10, 2026, 10:33 a.m.