Triple
T32136350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harima Province |
E820771
|
entity |
| Predicate | hadBuddhistProvincialTemple |
P173616
|
FINISHED |
| Object | Harima Kokubun-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: Harima Kokubun-ji | Statement: [Harima Province, hadBuddhistProvincialTemple, Harima Kokubun-ji]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadBuddhistProvincialTemple Context triple: [Harima Province, hadBuddhistProvincialTemple, Harima Kokubun-ji]
-
A.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
B.
hasTempleDistrict
Indicates that a place or settlement contains or is associated with a designated temple district area.
-
C.
hasHistoricTemple
Indicates that an entity possesses, contains, or is associated with a temple of historical significance.
-
D.
hasNotableTemple
Indicates that an entity is associated with a temple that is recognized as particularly important, famous, or significant.
-
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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9a9bc4c8190a88918fc4f91136a |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:30 a.m.