Triple
T12329067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honmon Butsuryu-shu |
E293909
|
entity |
| Predicate | hasPracticeGoal |
P88361
|
FINISHED |
| Object | personal transformation through chanting |
—
|
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: personal transformation through chanting | Statement: [Honmon Butsuryu-shu, hasPracticeGoal, personal transformation through chanting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPracticeGoal Context triple: [Honmon Butsuryu-shu, hasPracticeGoal, personal transformation through chanting]
-
A.
hasPractices
chosen
Indicates that an entity engages in, follows, or carries out specific practices, methods, or customary ways of doing things.
-
B.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
C.
hasGoalYear
Indicates that an entity is associated with a specific target year by which a goal or objective is intended to be achieved.
-
D.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
E.
hasHealthGoal
Indicates that an entity has a specific health-related objective or target it is aiming to achieve.
- 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.