Triple

T6174179
Position Surface form Disambiguated ID Type / Status
Subject Buna E137776 entity
Predicate near P350 FINISHED
Object Monowice E93706 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: Monowice | Statement: [Buna, near, Monowice]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Monowice
Context triple: [Buna, near, 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. 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.
  • D. 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.
  • E. Babia Góra
    Babia Góra is a prominent mountain on the Polish–Slovak border, renowned for its rugged landscapes, unique alpine flora, and status as a UNESCO-designated biosphere reserve.
  • 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_69c008a68c508190a8d78245c865960e completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c05d94c47481909745b2533926a1ca completed March 22, 2026, 9:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69c16ef0f76881909d678010d0c064e7 completed March 23, 2026, 4:48 p.m.
Created at: March 22, 2026, 4:18 p.m.