Triple
T7608212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hiromine Shrine |
E180161
|
entity |
| Predicate | hasPrimaryLanguageOfRitual |
P3115
|
FINISHED |
| Object | Japanese |
—
|
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: Japanese | Statement: [Hiromine Shrine, hasPrimaryLanguageOfRitual, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryLanguageOfRitual Context triple: [Hiromine Shrine, hasPrimaryLanguageOfRitual, Japanese]
-
A.
languageUsedInRituals
Indicates that a particular language is employed as the medium of speech, chant, or recitation during specific rituals or ceremonial practices.
-
B.
languageOfCeremony
Indicates the language in which a ceremony is conducted or officially performed.
-
C.
hasClericalLanguage
Indicates that something is expressed using formal, religious, or church-related language or terminology.
-
D.
usesPrimaryLiturgicalLanguageHistorically
Indicates that an entity has historically used a particular primary liturgical language in its religious rites or worship practices.
-
E.
languageOfWorship
chosen
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6fa1de8a4819091f9e9347835ce16 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:54 p.m.