Triple

T36962203
Position Surface form Disambiguated ID Type / Status
Subject Kreisau Circle E914333 entity
Predicate membersExecutedAt P80465 FINISHED
Object Plötzensee Prison NE NERFINISHED

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: Plötzensee Prison | Statement: [Kreisau Circle, membersExecutedAt, Plötzensee Prison]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: membersExecutedAt
Context triple: [Kreisau Circle, membersExecutedAt, Plötzensee Prison]
  • A. someMembersExecutedAt chosen
    Indicates that some, but not necessarily all, members of a group were subjected to execution at a particular time or place.
  • B. someMembersExecutedOn
    Indicates that at least one member of a group was subjected to execution in relation to a specified event or context.
  • C. memberExecutedBy
    Indicates that the execution or carrying out of a member (e.g., a task, operation, or component) is performed by a specific agent or executor.
  • D. someMembersExecutedBy
    Indicates that within a group or collection, at least some of its members are subjected to an execution carried out by a specified agent or process.
  • E. membersTriedAt
    Indicates that certain members of a group were subjected to a trial, hearing, or formal adjudicative process at a specified time or place.
  • 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_69f76e8c498c8190b2842db80aea8b3b completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fdb04ed81c8190b8feea90c1c785a6 completed May 8, 2026, 9:43 a.m.
PD Predicate disambiguation batch_69fda9d6c5148190a63205b6d9b0a1b4 completed May 8, 2026, 9:16 a.m.
Created at: May 3, 2026, 4:14 p.m.