Triple

T733976
Position Surface form Disambiguated ID Type / Status
Subject Auschwitz III-Monowitz E14890 entity
Predicate hasPrisonerPopulation P19522 FINISHED
Object primarily Jews LITERAL 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: primarily Jews | Statement: [Auschwitz III-Monowitz, hasPrisonerPopulation, primarily Jews]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPrisonerPopulation
Context triple: [Auschwitz III-Monowitz, hasPrisonerPopulation, primarily Jews]
  • A. numberOfPrisonersApproximate
    Indicates an approximate count of prisoners associated with an entity or situation, rather than an exact number.
  • B. estimatedPrisonerCount
    Indicates the estimated number of prisoners associated with a particular context, such as a location, time period, or event.
  • C. estimatedPrisoners
    Indicates a relationship where a value represents the estimated number of prisoners associated with a particular entity or context.
  • D. hasPopulationStatus
    Indicates the current demographic condition or classification of a population associated with an entity.
  • E. hasBeenImprisonedBy
    Indicates that one entity has been confined or incarcerated under the authority or control of another entity.
  • F. None of above. chosen

Provenance (4 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_69a4934d9930819099eed80096b0597d completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a66820548190b373deb117187c2c completed March 1, 2026, 8:49 p.m.
PD Predicate disambiguation batch_69a4a4fafee081909bf356854c09aaff completed March 1, 2026, 8:43 p.m.
PDg Predicate description generation batch_69a4a66658948190bdae6e521951954f completed March 1, 2026, 8:49 p.m.
Created at: March 1, 2026, 7:37 p.m.