Triple

T12854561
Position Surface form Disambiguated ID Type / Status
Subject Łužica E307414 entity
Predicate hasSubregion P285 FINISHED
Object Hornja Łužica E307414 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: Hornja Łužica | Statement: [Łužica, hasSubregion, Hornja Łužica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hornja Łužica
Context triple: [Łužica, hasSubregion, Hornja Łužica]
  • A. Łužica chosen
    Łužica is the Upper Sorbian name for Lusatia, a historical region in Central Europe traditionally inhabited by the West Slavic Sorbian people.
  • B. Noteć Dolna
    Noteć Dolna is the lower course and surrounding valley region of the Noteć River in north-central Poland, known for its wetlands and agricultural landscapes.
  • C. Huczwa
    Huczwa is a river in eastern Poland that flows through the Lublin region before joining the Western Bug.
  • D. Monowice
    Monowice is a village in southern Poland that became historically significant as the site of the Nazi German Auschwitz III-Monowitz labor camp during World War II.
  • E. Sucha Beskidzka
    Sucha Beskidzka is a small historic town in southern Poland, known for its picturesque Beskid mountain setting and its Renaissance-style castle.
  • 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_69d7bdf5e7cc8190be357278bc5ba3bb completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d97021df7481909cd42a0f72040aa5 completed April 10, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69f69ba79918819093e047ce22191923 completed May 3, 2026, 12:49 a.m.
Created at: April 9, 2026, 5:37 p.m.