Triple

T26585826
Position Surface form Disambiguated ID Type / Status
Subject Josephinist religious policy E667206 entity
Predicate hasLanguageLabel P151534 FINISHED
Object German: josephinische Kirchenpolitik 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: German: josephinische Kirchenpolitik | Statement: [Josephinist religious policy, hasLanguageLabel, German: josephinische Kirchenpolitik]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLanguageLabel
Context triple: [Josephinist religious policy, hasLanguageLabel, German: josephinische Kirchenpolitik]
  • A. labelNameLanguage chosen
    Indicates the language in which a given label or name is expressed.
  • B. hasLanguageRepresentation
    Indicates that an entity is expressed, encoded, or represented using a particular natural or formal language.
  • C. hasLanguageOn
    Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
  • D. hasLanguageStatus
    Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
  • E. hasLanguageType
    Indicates that an entity is associated with a particular type or category of language (e.g., spoken, written, programming, sign).
  • 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_69ee9cfb7e548190b60a9031182f5a7e completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69f72921cf2c8190909bb53f78bcc890 completed May 3, 2026, 10:53 a.m.
PD Predicate disambiguation batch_69f7283d8cec8190b524c144948bc4ec completed May 3, 2026, 10:49 a.m.
Created at: April 27, 2026, 2:05 a.m.