Triple

T35425179
Position Surface form Disambiguated ID Type / Status
Subject Leipzig-Heiterblick subcamp E1023898 entity
Predicate hasGuardingOrganization P76000 FINISHED
Object SS guards 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: SS guards | Statement: [Leipzig-Heiterblick subcamp, hasGuardingOrganization, SS guards]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGuardingOrganization
Context triple: [Leipzig-Heiterblick subcamp, hasGuardingOrganization, SS guards]
  • A. hasSupervisingOrganization
    Indicates that an entity is overseen, managed, or directed by a specific supervising organization.
  • B. hasOrganizationFor
    Indicates that one entity possesses, is associated with, or is responsible for a particular organization in relation to some context or purpose.
  • C. guardianInstitution chosen
    Indicates that an institution serves as a guardian or protective authority responsible for the care, oversight, or safeguarding of another entity.
  • D. hasResidentOrganization
    Indicates that an organization is based in, operates from, or maintains a primary presence within a particular place or facility.
  • E. hasNearbyProtectedAreaManagingOrganization
    Indicates that an entity has a managing organization responsible for a protected area located nearby.
  • 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_69f76df6704081909900c60be10d5849 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79da9f80c8190b0afd8509f28747b completed May 3, 2026, 7:10 p.m.
PD Predicate disambiguation batch_69f79617d40481909ba372f94209c08b completed May 3, 2026, 6:38 p.m.
Created at: May 3, 2026, 4:03 p.m.