Triple
T28885280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakusan shrines |
E732541
|
entity |
| Predicate | mainShrineLocatedIn |
P27586
|
FINISHED |
| Object | Hakusan, Ishikawa Prefecture |
—
|
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: Hakusan, Ishikawa Prefecture | Statement: [Hakusan shrines, mainShrineLocatedIn, Hakusan, Ishikawa Prefecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainShrineLocatedIn Context triple: [Hakusan shrines, mainShrineLocatedIn, Hakusan, Ishikawa Prefecture]
-
A.
majorShrineLocation
chosen
Indicates that a major religious shrine is located at or associated with a particular place or geographic location.
-
B.
shrineCity
Indicates that a city is the location of, or is associated with, a particular shrine.
-
C.
stateShrineOf
Indicates that one entity is officially designated as a state-recognized shrine associated with or located within another entity (typically a state or region).
-
D.
hasMajorShrine
Indicates that one entity serves as a principal or primary shrine dedicated to another entity.
-
E.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 7:49 a.m.