Triple
T25251921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shokoku-ji |
E632762
|
entity |
| Predicate | hasSubtemple |
P42500
|
FINISHED |
| Object | Jotenkaku Museum |
—
|
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: Jotenkaku Museum | Statement: [Shokoku-ji, hasSubtemple, Jotenkaku Museum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubtemple Context triple: [Shokoku-ji, hasSubtemple, Jotenkaku Museum]
-
A.
hasSubTemple
chosen
Indicates that one temple includes or contains another temple as a subordinate or component temple within its structure or organization.
-
B.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
C.
hasInnerShrine
Indicates that one entity contains or includes another entity that functions as an inner shrine within it.
-
D.
hasTempleFeature
Indicates that an entity possesses a specific architectural or structural feature characteristic of a temple.
-
E.
hasTempleLocation
Indicates that a temple is located at or associated with a specific place or geographic location.
- 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_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 21, 2026, 1:11 p.m.