Triple
T2736838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nichiren Buddhism |
E60648
|
entity |
| Predicate | languageOfChant |
P41747
|
FINISHED |
| Object | classical Japanese pronunciation of Sino-Japanese characters |
—
|
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: classical Japanese pronunciation of Sino-Japanese characters | Statement: [Nichiren Buddhism, languageOfChant, classical Japanese pronunciation of Sino-Japanese characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfChant Context triple: [Nichiren Buddhism, languageOfChant, classical Japanese pronunciation of Sino-Japanese characters]
-
A.
hasChant
Indicates that an entity is associated with or characterized by a particular chant.
-
B.
alsoChantedIn
Indicates that a chant, hymn, or recitation is performed or used in an additional context, location, or tradition beyond its primary one.
-
C.
languageOfCeremony
Indicates the language in which a ceremony is conducted or officially performed.
-
D.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
E.
lyricsLanguage
Indicates the language in which the lyrics of a song or musical work are written or performed.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb11c66c81909058f2978aa5fae9 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd968b2148190929af432c9d8001f |
completed | March 7, 2026, 7:53 a.m. |
Created at: March 6, 2026, 9:56 p.m.