Triple

T25251925
Position Surface form Disambiguated ID Type / Status
Subject Shokoku-ji E632762 entity
Predicate affiliatedTemple P13905 FINISHED
Object Ginkaku-ji NE NERFINISHED

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: Ginkaku-ji | Statement: [Shokoku-ji, affiliatedTemple, Ginkaku-ji]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: affiliatedTemple
Context triple: [Shokoku-ji, affiliatedTemple, Ginkaku-ji]
  • A. associatedTemple chosen
    Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
  • B. associatedShrine
    Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
  • C. associatedShrineComplex
    Indicates that one entity is linked or connected to a particular shrine complex, typically through location, function, or religious association.
  • D. associatedWithTempleComplex
    Indicates a relationship in which an entity is connected or related to a specific temple complex, such as by location, function, use, or historical association.
  • E. religiousAffiliationOfShrine
    Indicates the religious tradition or denomination with which a shrine is associated or dedicated.
  • 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_69e75a8fdd3881909ba0b05aa5da92a7 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f4808b8ab08190b48cca8408c88bdf completed May 1, 2026, 10:29 a.m.
PD Predicate disambiguation batch_69f45d06d0388190b36ecde92013624a completed May 1, 2026, 7:57 a.m.
Created at: April 21, 2026, 1:11 p.m.