Triple

T13347446
Position Surface form Disambiguated ID Type / Status
Subject Gmina Zembrzyce E317989 entity
Predicate containsSettlement P847 FINISHED
Object Zembrzyce E1252308 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: Zembrzyce | Statement: [Gmina Zembrzyce, containsSettlement, Zembrzyce]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zembrzyce
Context triple: [Gmina Zembrzyce, containsSettlement, Zembrzyce]
  • A. Zembrzyce chosen
    Zembrzyce is a village in southern Poland that serves as the local administrative and cultural hub of its surrounding rural area.
  • B. Zbrzyca
    Zbrzyca is a river in northern Poland that flows through the Pomeranian region before joining the Brda River.
  • C. Brzesko
    Brzesko is a town in southern Poland known for its historical architecture and regional brewing traditions.
  • D. Zambrów
    Zambrów is a town in northeastern Poland known for its agricultural surroundings and location along important regional transport routes.
  • E. Zebrzydowice
    Zebrzydowice is a village and administrative seat in southern Poland, located in the Silesian Voivodeship near the Czech border.
  • 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_69d806b5a3c08190b42c267fb092f98a completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d99e8b28e48190a23194e03a74b41b completed April 11, 2026, 1:06 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0167369d9481909015c34d475fac14 completed May 11, 2026, 5:20 a.m.
Created at: April 9, 2026, 9:31 p.m.