Triple

T27971276
Position Surface form Disambiguated ID Type / Status
Subject Reitaisai (grand festival) E706361 entity
Predicate associatedShrineRank P27875 FINISHED
Object ichinomiya of Buzen Province 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 of Buzen Province | Statement: [Reitaisai (grand festival), associatedShrineRank, ichinomiya of Buzen Province]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedShrineRank
Context triple: [Reitaisai (grand festival), associatedShrineRank, ichinomiya of Buzen Province]
  • A. shrineRank
    Indicates the hierarchical or status level assigned to a shrine relative to other shrines.
  • B. associatedShrine chosen
    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. recognizedAsShrineBy
    Indicates that something is regarded or designated as a shrine by a particular person, group, or authority.
  • E. shrineType
    Indicates the specific category or kind of shrine associated with an entity.
  • 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_69ef96b7f330819090f315318ba6977e completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_6a009f53a4948190aef4ede1713e1748 completed May 10, 2026, 3:08 p.m.
PD Predicate disambiguation batch_6a009edc53d4819080b22c1074a990f3 completed May 10, 2026, 3:06 p.m.
Created at: April 27, 2026, 7:38 p.m.