Triple

T733985
Position Surface form Disambiguated ID Type / Status
Subject Auschwitz III-Monowitz E14890 entity
Predicate hasLivingConditions P1255 FINISHED
Object extremely harsh 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: extremely harsh | Statement: [Auschwitz III-Monowitz, hasLivingConditions, extremely harsh]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLivingConditions
Context triple: [Auschwitz III-Monowitz, hasLivingConditions, extremely harsh]
  • A. hasLivingEnvironment
    Indicates that an entity exists or resides within a particular living environment or habitat.
  • B. isLiving
    Indicates that an entity is currently alive or possesses life.
  • C. environmentalCondition
    Indicates the state or characteristics of the surrounding physical environment that affect or describe a situation, process, or entity.
  • D. hasCondition chosen
    Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
  • E. hasClimate
    Indicates that an entity possesses or is characterized by a particular type of climate or climatic conditions.
  • F. None of above.

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_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.
Created at: March 1, 2026, 7:37 p.m.