Triple
T23980665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shinobazu Pond |
E604497
|
entity |
| Predicate | religiousAffiliationOfShrine |
P154116
|
FINISHED |
| Object | Buddhism |
—
|
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: Buddhism | Statement: [Shinobazu Pond, religiousAffiliationOfShrine, Buddhism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousAffiliationOfShrine Context triple: [Shinobazu Pond, religiousAffiliationOfShrine, Buddhism]
-
A.
religiousAffiliationOfMainShrine
Indicates the religion or faith tradition with which the main shrine is affiliated.
-
B.
enshrines
Indicates that one entity formally preserves, protects, or honors another by giving it a permanent, often sacred or legally recognized, status.
-
C.
shrineSignificance
Indicates the cultural, religious, or historical importance attributed to a particular shrine within its context.
-
D.
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).
-
E.
shrineType
Indicates the specific category or kind of shrine associated with an entity.
- 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2bd58448190a64e7a9020109229 |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:27 p.m.