Triple

T30009615
Position Surface form Disambiguated ID Type / Status
Subject Espoo Cathedral E762420 entity
Predicate secondaryLanguageOfServices P194011 FINISHED
Object Swedish 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: Swedish | Statement: [Espoo Cathedral, secondaryLanguageOfServices, Swedish]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: secondaryLanguageOfServices
Context triple: [Espoo Cathedral, secondaryLanguageOfServices, Swedish]
  • A. secondaryLanguageSupport chosen
    Indicates that an entity provides assistance, services, or functionality in an additional (non-primary) language.
  • B. laterSecondaryLanguageOfAdministration
    Indicates that one language served as a subsequent or later secondary language used for administrative purposes in relation to another language.
  • C. secondaryLanguageContext
    Indicates that the associated information, interaction, or content occurs within or is tailored to a secondary (non-primary) language setting or usage context.
  • D. primaryLanguageSide2
    Indicates that the second entity in the relationship uses or is associated with the primary language specified.
  • E. hasSecondaryLanguage
    Indicates that an entity possesses or uses a secondary language in addition to its primary language.
  • 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_69f2246b0c84819094f1250b6a02d277 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69fd8ccbd4c88190b13aae0673b3c821 completed May 8, 2026, 7:12 a.m.
PD Predicate disambiguation batch_69fd8ae2227c819089546f5c3629799e completed May 8, 2026, 7:04 a.m.
Created at: April 29, 2026, 6:43 p.m.