Triple
T37509432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of the Holy Light |
E932178
|
entity |
| Predicate | viewsHolyLightAs |
P5490
|
FINISHED |
| Object | benevolent cosmic force |
—
|
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: benevolent cosmic force | Statement: [Church of the Holy Light, viewsHolyLightAs, benevolent cosmic force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewsHolyLightAs Context triple: [Church of the Holy Light, viewsHolyLightAs, benevolent cosmic force]
-
A.
viewOfHolySpirit
Indicates a relationship where an entity holds a particular belief, doctrine, or perspective about the nature, role, or attributes of the Holy Spirit.
-
B.
viewOfGod
chosen
Indicates a relationship where an entity holds a particular conception, perspective, or understanding of God.
-
C.
viewOnHeaven
Indicates a relationship where an entity holds a particular perspective, opinion, or belief about heaven.
-
D.
viewOnSanctification
Indicates a person's doctrinal or theological stance regarding the process and nature of sanctification.
-
E.
viewOnWorship
Indicates a relationship where one entity holds a particular stance, opinion, or doctrinal position regarding the practice or concept of worship.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.