Triple
T27004618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 金光教 |
E680207
|
entity |
| Predicate | 教義の中心概念 |
P106177
|
FINISHED |
| Object | 信心生活 |
—
|
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: 信心生活 | Statement: [金光教, 教義の中心概念, 信心生活]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 教義の中心概念 Context triple: [金光教, 教義の中心概念, 信心生活]
-
A.
theologicalConcept
Indicates that something is a religious or theological idea, doctrine, or principle within a belief system.
-
B.
doctrinalTerm
Indicates that one entity is a doctrinal or theological term that conceptually characterizes, labels, or defines the other entity within a religious or ideological system.
-
C.
doctrinalSignificance
Indicates the importance or impact that a doctrine or set of teachings has within a particular religious, legal, or ideological system.
-
D.
doctrinalEmphasis
Indicates a relationship where a doctrine, belief system, or teaching is given particular focus, priority, or stress within a religious, ideological, or organizational context.
-
E.
focusOfTeachings
chosen
Indicates that the object is the primary subject or central theme emphasized in the teachings of the subject.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 7 a.m.