Triple

T36127336
Position Surface form Disambiguated ID Type / Status
Subject Hubermann house on Himmel Street E1044917 entity
Predicate riskTakenByInhabitants P59284 FINISHED
Object hiding a Jewish man 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: hiding a Jewish man | Statement: [Hubermann house on Himmel Street, riskTakenByInhabitants, hiding a Jewish man]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: riskTakenByInhabitants
Context triple: [Hubermann house on Himmel Street, riskTakenByInhabitants, hiding a Jewish man]
  • A. riskTakenFor
    Indicates that one entity accepts or undertakes a risk for the benefit, protection, or sake of another entity.
  • B. riskTaken chosen
    Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
  • C. hasNaturalHazardRisk
    Indicates that an entity is exposed or subject to potential damage or impact from one or more natural hazards (e.g., earthquakes, floods, storms).
  • D. riskElement
    Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
  • E. riskZone
    Indicates that an entity is located within or associated with an area characterized by elevated danger, threat, or potential harm.
  • 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_69f76e356c908190abc6ca1e6a05b011 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b3e2f3c08190be4fd1ae4fa1266d completed May 3, 2026, 8:45 p.m.
PD Predicate disambiguation batch_69f7b1bcc47081909fe7d592ac69006c completed May 3, 2026, 8:36 p.m.
Created at: May 3, 2026, 4:08 p.m.