Triple

T21796693
Position Surface form Disambiguated ID Type / Status
Subject Catholic Church in Japan E538110 entity
Predicate mainLiturgicalLanguage P45911 FINISHED
Object Japanese 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: Japanese | Statement: [Catholic Church in Japan, mainLiturgicalLanguage, Japanese]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: mainLiturgicalLanguage
Context triple: [Catholic Church in Japan, mainLiturgicalLanguage, Japanese]
  • A. liturgicalLanguageVersion
    Indicates that one entity is a specific version or form of another entity expressed in a particular liturgical language.
  • B. liturgicalLanguageUsage chosen
    Indicates the relationship in which a particular language is used as the medium for conducting religious or liturgical rites, prayers, or ceremonies.
  • C. usesPrimaryLiturgicalLanguageHistorically
    Indicates that an entity has historically used a particular primary liturgical language in its religious rites or worship practices.
  • D. languageOfWorship
    Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
  • E. liturgicalFormIncludes
    Indicates that one liturgical form contains, incorporates, or makes use of another liturgical element or 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_69e0c4733f4081909a86622e7e6d15d2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f0622502188190998638317f232334 completed April 28, 2026, 7:30 a.m.
PD Predicate disambiguation batch_69e6be751ce881909badced245ef76c7 completed April 21, 2026, 12:01 a.m.
Created at: April 16, 2026, 6:53 p.m.