Triple
T12329007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kempon Hokke |
E293908
|
entity |
| Predicate | centralChant |
P15355
|
FINISHED |
| Object | Namu Myōhō Renge Kyō |
—
|
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: Namu Myōhō Renge Kyō | Statement: [Kempon Hokke, centralChant, Namu Myōhō Renge Kyō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralChant Context triple: [Kempon Hokke, centralChant, Namu Myōhō Renge Kyō]
-
A.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
B.
centralName
Indicates that the specified name serves as the primary or main identifying label within a given context or naming structure.
-
C.
hasChant
chosen
Indicates that an entity is associated with or characterized by a particular chant.
-
D.
centralEventOfPiety
Indicates that an event serves as the primary or focal act of religious devotion or pious practice within a given context.
-
E.
centralCharge
Indicates that an entity has a specific central charge value, typically quantifying a key parameter in a conformal or related physical or mathematical theory.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.