Triple

T372100
Position Surface form Disambiguated ID Type / Status
Subject Belzec E8288 entity
Predicate hasSurvivors P11769 FINISHED
Object very few known survivors 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: very few known survivors | Statement: [Belzec, hasSurvivors, very few known survivors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSurvivors
Context triple: [Belzec, hasSurvivors, very few known survivors]
  • A. hasSurvivorTerm
    Indicates that an entity is associated with a term or label specifically used to describe survivors of an event, condition, or circumstance.
  • B. hasSurvivingOriginals
    Indicates that some of the original instances or versions of an entity still exist and have not been lost, destroyed, or replaced.
  • C. survivorTerm
    Indicates that one entity is designated as the surviving or remaining party in relation to another entity, often after a loss, termination, or adverse event.
  • D. survivingStructure
    Indicates that a structure continues to exist or remain intact after a potentially destructive event or over a significant period of time.
  • E. survivedEvent
    Indicates that an entity continued to live or exist after experiencing and not being destroyed or killed by a particular event.
  • 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_69a2e7f2ec648190b42bc7db424f8109 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec00785481908551fc3571fcca47 completed Feb. 28, 2026, 1:22 p.m.
PD Predicate disambiguation batch_69a2e960d880819084b3df4e5137a1e2 completed Feb. 28, 2026, 1:10 p.m.
PDg Predicate description generation batch_69a2ea0b23ec8190bef9d593162388a4 completed Feb. 28, 2026, 1:13 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.