Triple
T7646925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Konkokyo |
E173147
|
entity |
| Predicate | hasViewOnDeity |
P5608
|
FINISHED |
| Object | deity is benevolent and immanent in the universe |
—
|
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: deity is benevolent and immanent in the universe | Statement: [Konkokyo, hasViewOnDeity, deity is benevolent and immanent in the universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViewOnDeity Context triple: [Konkokyo, hasViewOnDeity, deity is benevolent and immanent in the universe]
-
A.
hasDeity
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
B.
hasViewOnDivinity
chosen
Indicates that an entity holds a particular belief, opinion, or perspective regarding divinity or the nature of the divine.
-
C.
hasDeityAspect
Indicates that one entity embodies, represents, or functions as a specific divine aspect or manifestation of another deity.
-
D.
viewOnOtherDeities
Indicates how one deity regards, evaluates, or conceptually relates to other deities.
-
E.
appliesToDeityIn
Indicates that something (such as a rule, attribute, or statement) is relevant or applicable to a deity within a specified context or domain.
- 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_69c6995360188190968ee57b72a1627f |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faf3bd388190a8cb0f13322a7c00 |
completed | March 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e9ef1c81909c8bff716541ac1f |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:58 p.m.