Triple

T18281041
Position Surface form Disambiguated ID Type / Status
Subject Monowitz labor camp E437863 entity
Predicate locatedIn P40 FINISHED
Object Monowice 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: Monowice | Statement: [Monowitz labor camp, locatedIn, Monowice]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Monowice
Context triple: [Monowitz labor camp, locatedIn, Monowice]
  • A. Monowice chosen
    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.
  • B. Sucha Beskidzka
    Sucha Beskidzka is a small historic town in southern Poland, known for its picturesque Beskid mountain setting and its Renaissance-style castle.
  • C. Borowa Góra
    Borowa Góra is a locality in central Poland known primarily as the site of a World War II battle between Polish and German forces in September 1939.
  • D. Szklarska Poręba
    Szklarska Poręba is a popular Polish mountain resort town known for skiing, hiking, and scenic landscapes in the Karkonosze range near the Czech border.
  • E. Maków Beskids
    Maków Beskids is a mountain range in the Western Beskids of southern Poland, known for its rolling forested hills and small towns.
  • 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_69d8b914530c8190b4474d862a2b2a1b completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e50056ea0481908d66bf263ac80c75 completed April 19, 2026, 4:18 p.m.
Created at: April 10, 2026, 10:35 a.m.