Triple
T33177143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hokkedō |
E849210
|
entity |
| Predicate | mountainTempleContext |
P176155
|
FINISHED |
| Object | Hieizan (Mount Hiei) temple network |
—
|
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: Hieizan (Mount Hiei) temple network | Statement: [Hokkedō, mountainTempleContext, Hieizan (Mount Hiei) temple network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainTempleContext Context triple: [Hokkedō, mountainTempleContext, Hieizan (Mount Hiei) temple network]
-
A.
holyMountain
Indicates that a mountain is regarded as sacred or religiously significant within a particular belief system or tradition.
-
B.
hillTemple
Indicates a relationship where a temple is located on, associated with, or dedicated to a hill.
-
C.
mainTemple
Indicates that one entity serves as the primary or central temple associated with another entity.
-
D.
templeCountry
Indicates that a temple is located within or belongs to a particular country.
-
E.
templeState
Indicates that a temple is in a particular condition, status, or phase (such as operational, under construction, abandoned, or ceremonial).
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:29 a.m.