Triple

T22340033
Position Surface form Disambiguated ID Type / Status
Subject Stadtholderless Periods E552247 entity
Predicate significantOfficeAbsent P14452 FINISHED
Object stadtholder 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: stadtholder | Statement: [Stadtholderless Periods, significantOfficeAbsent, stadtholder]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: significantOfficeAbsent
Context triple: [Stadtholderless Periods, significantOfficeAbsent, stadtholder]
  • A. lostOfficeBecauseOf
    Indicates that an entity ceased to hold an office or position as a consequence of another specified factor, event, or entity.
  • B. notableAbsence chosen
    Indicates that something or someone is conspicuously missing from a context where their presence would normally be expected or significant.
  • C. importantOffice
    Indicates that an entity holds or is associated with a position or office considered significant or high in importance within a given context.
  • D. significantAction
    Indicates that an action taken by an entity is of notable importance or consequence within a given context or process.
  • E. significantPort
    Indicates that a port holds major importance in terms of trade, transportation, or strategic relevance within a given context.
  • 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_69e11e494eec81909c4d2d51f69499d9 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f157824f588190882bea9e61dd5a83 completed April 29, 2026, 12:57 a.m.
PD Predicate disambiguation batch_69e7300c20088190a59e5bf9e70384f3 completed April 21, 2026, 8:06 a.m.
Created at: April 16, 2026, 8:43 p.m.