Triple

T27160169
Position Surface form Disambiguated ID Type / Status
Subject Kurozumi school of Shinto E682638 entity
Predicate scriptureOrText P11799 FINISHED
Object teachings of Kurozumi Munetada 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: teachings of Kurozumi Munetada | Statement: [Kurozumi school of Shinto, scriptureOrText, teachings of Kurozumi Munetada]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scriptureOrText
Context triple: [Kurozumi school of Shinto, scriptureOrText, teachings of Kurozumi Munetada]
  • A. scriptureFor
    Indicates that one entity serves as a scriptural or authoritative religious text for another entity (such as a person, group, or belief system).
  • B. scriptureType
    Indicates the classification or category of a scripture in relation to its type or genre.
  • C. scripturalCorpus chosen
    Indicates that one entity is a body of scriptural or sacred texts associated with, or serving as the canonical writings for, another entity.
  • D. scriptureRead
    Indicates that an entity reads, studies, or engages with a religious or sacred text.
  • E. recognizesScripturesFrom
    Indicates that one entity acknowledges or accepts certain scriptures as authoritative or valid based on another entity as their source or origin.
  • 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_69eefacf6e788190a75a64399d9e3109 completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f6691f5e188190b12c7b2eb729a45e completed May 2, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69f66598d6008190a7ca8ff80399fd34 completed May 2, 2026, 8:59 p.m.
Created at: April 27, 2026, 9:18 a.m.