Triple

T33926392
Position Surface form Disambiguated ID Type / Status
Subject Beschlüsse der Landessynode der Evangelischen Landeskirche in Württemberg E869762 entity
Predicate Dokumenttyp P19006 FINISHED
Object Synodenprotokoll 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: Synodenprotokoll | Statement: [Beschlüsse der Landessynode der Evangelischen Landeskirche in Württemberg, Dokumenttyp, Synodenprotokoll]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: Dokumenttyp
Context triple: [Beschlüsse der Landessynode der Evangelischen Landeskirche in Württemberg, Dokumenttyp, Synodenprotokoll]
  • A. documentationType chosen
    Indicates the specific category or kind of documentation associated with or required for an entity or process.
  • B. draftType
    Indicates the specific category or kind of draft associated with an entity or document (e.g., initial, revised, or final draft).
  • C. documentTypeUsed
    Indicates that a particular type or category of document is employed or applied in a given context or activity.
  • D. documentTypeProduced
    Indicates that one entity produces, generates, or creates a document of a specified type.
  • E. documentsTypeOfStructure
    Indicates that an entity records or specifies the particular type or classification of a structure.
  • 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_69f349992c508190aa4afa24a086cc8c completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7064e906881909c3186c646145d34 completed May 3, 2026, 8:24 a.m.
PD Predicate disambiguation batch_69f70100ec1c8190a6b97f50e88891f2 completed May 3, 2026, 8:02 a.m.
Created at: May 1, 2026, 1:49 a.m.