Triple

T23954152
Position Surface form Disambiguated ID Type / Status
Subject Tomainian ghetto E603732 entity
Predicate instanceOf P0 FINISHED
Object fictional Jewish ghetto C47723 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: fictional Jewish ghetto
Context triple: [Tomainian ghetto, instanceOf, fictional Jewish ghetto]
  • A. Jewish ghetto inhabitant
    A Jewish ghetto inhabitant is a Jewish person forcibly confined to a segregated, restricted urban district under discriminatory laws or occupation, typically facing overcrowding, deprivation, and persecution.
  • B. World War II ghetto chosen
    A World War II ghetto was a segregated, enclosed urban district where Nazi authorities forcibly confined Jews (and sometimes other targeted groups) under overcrowded, impoverished, and brutal conditions as part of their broader system of persecution and genocide.
  • C. fictional underground community
    A fictional underground community is a hidden, self-contained society that exists beneath the surface world, often with its own culture, rules, and conflicts distinct from those above.
  • D. ghetto administration body
    A ghetto administration body is an authority structure, often imposed or controlled by an external regime, responsible for managing the daily governance, resources, and population regulation within a segregated and marginalized urban district.
  • E. historic Jewish quarter
    A historic Jewish quarter is an urban district where Jewish communities historically lived, worked, and worshipped, characterized by synagogues, cultural institutions, distinctive architecture, and remnants of religious and communal life.
  • F. None of above.

Provenance (1 batch)

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_69e2954222288190a7323554d0cca8d7 completed April 17, 2026, 8:17 p.m.
Created at: April 17, 2026, 9:21 p.m.