Triple

T8657651
Position Surface form Disambiguated ID Type / Status
Subject Osaka Tenmangū E205460 entity
Predicate hasPatronDeityType P51997 FINISHED
Object kami of learning 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: kami of learning | Statement: [Osaka Tenmangū, hasPatronDeityType, kami of learning]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPatronDeityType
Context triple: [Osaka Tenmangū, hasPatronDeityType, kami of learning]
  • A. hasDeity
    Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
  • B. hasDeityAspect
    Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another deity.
  • C. patronDeityOf chosen
    Indicates that one entity serves as the protective or primary deity associated with, worshipped by, or presiding over another entity (such as a person, group, or place).
  • D. hasComponentDeity
    Indicates that an entity (such as a religion, mythology, or pantheon) includes a particular deity as one of its constituent or associated divine figures.
  • E. hasDeityGroup
    Indicates a relationship where an entity is associated with, or belongs to, a particular group or pantheon of deities.
  • 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_69ca8350897c819086cde7596fbe5fe7 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc486d576081908ad28749c7971432 completed March 31, 2026, 10:19 p.m.
PD Predicate disambiguation batch_69cc45619460819091e83ffdec99c865 completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:30 p.m.