Triple
T14383411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 80: Kokubunji |
E356663
|
entity |
| Predicate | isSacredSite |
P21627
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Temple 80: Kokubunji, isSacredSite, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSacredSite Context triple: [Temple 80: Kokubunji, isSacredSite, yes]
-
A.
cultSite
chosen
Indicates a location that is or was used for religious or ritual worship activities.
-
B.
isArchaeologicalSite
Indicates that a location or structure is recognized as an archaeological site, typically due to its historical or cultural remains of past human activity.
-
C.
isPlaceOfPilgrimageFor
Indicates that a location serves as a destination for religious or spiritual pilgrimage for a person or group.
-
D.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
E.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de900d28c88190a37feee4743563de |
completed | April 14, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:16 a.m.