Triple
T15585774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishizuchi Shrine |
E374616
|
entity |
| Predicate | mountainWorship |
P103299
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ishizuchi Shrine, mountainWorship, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainWorship Context triple: [Ishizuchi Shrine, mountainWorship, true]
-
A.
worshipPeak
chosen
Indicates a relationship where an entity directs religious or spiritual reverence, devotion, or worship toward a particular peak or mountain.
-
B.
holyMountain
Indicates that a mountain is regarded as sacred or religiously significant within a particular belief system or tradition.
-
C.
worship
Indicates a relationship where one entity shows reverence, adoration, or religious devotion toward another entity, often recognizing it as sacred or divine.
-
D.
worshipFocus
Indicates that one entity directs religious reverence, devotion, or adoration toward another as the primary object of worship.
-
E.
worshipType
Indicates the manner or form in which worship is practiced or expressed in a religious or spiritual context.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e4900408190aadb48b001db4169 |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.