Triple

T24741975
Position Surface form Disambiguated ID Type / Status
Subject Gauleiter E618586 entity
Predicate oftenAlsoHeldOffice P42708 FINISHED
Object Oberpräsident 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: Oberpräsident | Statement: [Gauleiter, oftenAlsoHeldOffice, Oberpräsident]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: oftenAlsoHeldOffice
Context triple: [Gauleiter, oftenAlsoHeldOffice, Oberpräsident]
  • A. alsoHoldsOfficeOf
    Indicates that an entity currently holding one office or position simultaneously holds another office or position as well.
  • B. possibleOfficeHeld
    Indicates that an entity may have held, or is a candidate to have held, a particular office or position, without asserting it as a confirmed fact.
  • C. officeHoldersAlsoHeldPosition chosen
    Indicates that an individual who holds one office or position has also held another specified office or position (at some time, possibly earlier or later).
  • D. officeHolderMayAlsoBe
    Indicates that an individual holding one office or position is permitted or able to simultaneously hold another specified office or position.
  • E. hasHeldOfficeType
    Indicates that an entity has at some time occupied or served in a specified type or category of office or position.
  • 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_69e2fab8f95c81908bb9e552cf3280c2 completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f42d9000b8819081ea2605f3c193d6 completed May 1, 2026, 4:35 a.m.
PD Predicate disambiguation batch_69f420f471a0819095a6cd24ed8f7476 completed May 1, 2026, 3:41 a.m.
Created at: April 18, 2026, 4:17 a.m.