Triple

T21819533
Position Surface form Disambiguated ID Type / Status
Subject Naikū E538687 entity
Predicate innerSanctumAccess P15393 FINISHED
Object limited to priests and select individuals 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: limited to priests and select individuals | Statement: [Naikū, innerSanctumAccess, limited to priests and select individuals]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: innerSanctumAccess
Context triple: [Naikū, innerSanctumAccess, limited to priests and select individuals]
  • A. oneOfMultipleSanctums
    Indicates that an entity is one among several sanctums associated with or available to another entity.
  • B. hasMainSanctum
    Indicates that an entity possesses a primary or central sacred space used for core religious or spiritual activities.
  • C. sanctumContains
    Indicates that one sanctum or sacred space physically or conceptually includes or holds another entity within its bounds.
  • D. hasSanctuary
    Indicates that one entity provides or serves as a place of refuge, protection, or safe haven for another entity.
  • E. controlsAccessTo chosen
    Indicates that one entity regulates, manages, or determines the ability of another entity to reach, use, or interact with a resource, location, or service.
  • 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_69e0c475038c8190abb9b1a20eb8ff50 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f07cce0b8081909e20ded72db40304 completed April 28, 2026, 9:24 a.m.
PD Predicate disambiguation batch_69e6be815a108190be81d7c987d0c0d6 completed April 21, 2026, 12:02 a.m.
Created at: April 16, 2026, 6:54 p.m.