Triple
T38651719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakone Shrine |
E939771
|
entity |
| Predicate | hasObjectOfWorship |
P2291
|
FINISHED |
| Object | Mount Hakone |
—
|
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: Mount Hakone | Statement: [Hakone Shrine, hasObjectOfWorship, Mount Hakone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasObjectOfWorship Context triple: [Hakone Shrine, hasObjectOfWorship, Mount Hakone]
-
A.
isWorshippedFor
Indicates that one entity is revered or honored by another specifically because of a particular quality, deed, or attribute.
-
B.
worshippedIn
chosen
Indicates that a particular deity, figure, or object of reverence is the focus of religious or spiritual worship within a specified place or context.
-
C.
worshipsDeity
Indicates that one entity reveres, honors, or performs religious devotion toward another entity regarded as a deity.
-
D.
hasReligiousObject
Indicates that an entity possesses, is associated with, or contains a religious object (such as an artifact, symbol, or item used in religious practice).
-
E.
isPlaceOfWorshipFor
Indicates that a location serves as a site where members of a particular religion or belief system perform worship or religious practices.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.