Triple
T28885302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakusan shrines |
E732541
|
entity |
| Predicate | relatedShrineNetwork |
P184540
|
FINISHED |
| Object | Hie shrines |
—
|
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: Hie shrines | Statement: [Hakusan shrines, relatedShrineNetwork, Hie shrines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedShrineNetwork Context triple: [Hakusan shrines, relatedShrineNetwork, Hie shrines]
-
A.
associatedShrine
Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
-
B.
shrineNetwork
chosen
Indicates a relationship where shrines are connected or linked together as part of a shared network or system.
-
C.
associatedShrineComplex
Indicates that one entity is linked or connected to a particular shrine complex, typically through location, function, or religious association.
-
D.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
E.
influencedShrines
Indicates that one entity had an effect on the design, function, significance, or development of certain shrines.
- 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_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
Created at: April 28, 2026, 7:49 a.m.