Triple

T28885143
Position Surface form Disambiguated ID Type / Status
Subject Hakusan Okami E732538 entity
Predicate worshippedAt P2291 FINISHED
Object Hakusan Jinja
Hakusan Jinja is a Shinto shrine in Japan dedicated to the mountain and nature kami associated with Mount Hakusan, serving as a center of regional worship and pilgrimage.
E678113 NE 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: Hakusan Jinja | Statement: [Hakusan Okami, worshippedAt, Hakusan Jinja]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Hakusan Jinja
Triple: [Hakusan Okami, worshippedAt, Hakusan Jinja]
Generated description
Hakusan Jinja is a Shinto shrine in Japan dedicated to the mountain and nature kami associated with Mount Hakusan, serving as a center of regional worship and pilgrimage.

Provenance (5 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_69f05b07bdec819080cadfe147aa1f25 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f65a70930081908e83cbf463357207 completed May 2, 2026, 8:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a418521eb0c81908464452a197e4967 completed June 28, 2026, 8:33 p.m.
NEDg Description generation batch_6a418614ac648190bdad4426fee791fb completed June 28, 2026, 8:37 p.m.
NED2 Entity disambiguation (via description) batch_6a4186d235348190a89738f739b88fdb completed June 28, 2026, 8:40 p.m.
Created at: April 28, 2026, 7:49 a.m.