Triple

T8641643
Position Surface form Disambiguated ID Type / Status
Subject Maarkedal E204664 entity
Predicate hasSubMunicipality P747 FINISHED
Object Etikhove E747373 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: Etikhove | Statement: [Maarkedal, hasSubMunicipality, Etikhove]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Etikhove
Context triple: [Maarkedal, hasSubMunicipality, Etikhove]
  • A. Etikhove chosen
    Etikhove is a village in East Flanders, Belgium, now part of the municipality of Maarkedal and known for its rural landscape and traditional Flemish character.
  • B. Berdichev
    Berdichev is a historic city in present-day Ukraine, long known as a major center of Jewish life and commerce in Eastern Europe.
  • C. Radomyshl
    Radomyshl is a historic town in northern Ukraine, known for its Jewish heritage and role within the Zhytomyr Oblast region.
  • D. Horokhiv
    Horokhiv is a small town in western Ukraine known for its location within the historic Volyn region.
  • E. Kremenets
    Kremenets is a historic town in western Ukraine known for its rich cultural heritage and once-significant Jewish community.
  • 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_69ca834ca1c88190a11ffb0200342fac completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc4795b07081908bfc9ebf35a50f07 completed March 31, 2026, 10:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69ceccb10f0881908db334cd090d3231 completed April 2, 2026, 8:08 p.m.
Created at: March 30, 2026, 6:28 p.m.