Triple

T33898925
Position Surface form Disambiguated ID Type / Status
Subject Tagitsuhime-no-Mikoto E868991 entity
Predicate hasShrineCategory P182283 FINISHED
Object ichinomiya (provincial primary shrine, via Munakata Taisha) 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: ichinomiya (provincial primary shrine, via Munakata Taisha) | Statement: [Tagitsuhime-no-Mikoto, hasShrineCategory, ichinomiya (provincial primary shrine, via Munakata Taisha)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasShrineCategory
Context triple: [Tagitsuhime-no-Mikoto, hasShrineCategory, ichinomiya (provincial primary shrine, via Munakata Taisha)]
  • A. containsShrine
    Indicates that one entity includes or has within its boundaries a shrine associated with it.
  • B. hasShrinesIn
    Indicates that one entity possesses or maintains shrines that are located within the area or domain of another entity.
  • C. hasShrines
    Indicates that one entity contains, hosts, or is associated with one or more shrines dedicated to another entity.
  • D. hasSubshrineType
    Indicates that an entity includes or is associated with a subshrine of a specified type.
  • E. hasInnerShrine
    Indicates that one entity contains or includes another entity that functions as an inner shrine within it.
  • F. None of above. chosen

Provenance (4 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_69f34997703c8190866b1d404bce531f completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f7886be6d8819095ec62e4f2cee858 completed May 3, 2026, 5:39 p.m.
PD Predicate disambiguation batch_69f7841440f48190b4346c08855951d2 completed May 3, 2026, 5:21 p.m.
PDg Predicate description generation batch_69f7886b27f08190ab4580f949222c93 completed May 3, 2026, 5:39 p.m.
Created at: May 1, 2026, 1:48 a.m.