Triple
T12328963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nam-myoho-renge-kyo |
E293907
|
entity |
| Predicate | fullMeaning |
P92178
|
FINISHED |
| Object | Devotion to the Mystic Law of the Lotus Sutra |
—
|
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: Devotion to the Mystic Law of the Lotus Sutra | Statement: [Nam-myoho-renge-kyo, fullMeaning, Devotion to the Mystic Law of the Lotus Sutra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullMeaning Context triple: [Nam-myoho-renge-kyo, fullMeaning, Devotion to the Mystic Law of the Lotus Sutra]
-
A.
overallMeaning
Indicates the general or overarching significance, interpretation, or message conveyed by something as a whole.
-
B.
commonMeaning
Indicates that multiple entities share the same or very similar meaning or semantic interpretation.
-
C.
logicalMeaning
Indicates that one entity expresses, encodes, or conveys the logical content, implication, or formal meaning of another.
-
D.
textMeaning
Indicates that one text expresses, conveys, or corresponds to a particular meaning or semantic content.
-
E.
basicMeaning
chosen
Indicates that one entity expresses or conveys the fundamental or core meaning of another entity.
- 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.