Triple
T8404204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaga Ichinomiya Shirayama Hime Shrine |
E198452
|
entity |
| Predicate | chiefShrineOf |
P21389
|
FINISHED |
| Object | former Kaga 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: former Kaga Province | Statement: [Kaga Ichinomiya Shirayama Hime Shrine, chiefShrineOf, former Kaga Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chiefShrineOf Context triple: [Kaga Ichinomiya Shirayama Hime Shrine, chiefShrineOf, former Kaga Province]
-
A.
enshrines
Indicates that one entity formally preserves, protects, or honors another by giving it a permanent, often sacred or legally recognized, status.
-
B.
hasMajorShrine
chosen
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
-
C.
shrineType
Indicates the specific category or kind of shrine associated with an entity.
-
D.
foundedAsShrine
Indicates that an entity was originally established or created as a shrine.
-
E.
majorShrineLocation
Indicates that a major religious shrine is located at or associated with a particular 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83116bf48190894bd5d5465520ef |
completed | March 31, 2026, 8:17 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.