Triple
T20692713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debata Mula Jadi Nabolon |
E508589
|
entity |
| Predicate | theologicalType |
P5493
|
FINISHED |
| Object | high god |
—
|
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: high god | Statement: [Debata Mula Jadi Nabolon, theologicalType, high god]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theologicalType Context triple: [Debata Mula Jadi Nabolon, theologicalType, high god]
-
A.
theologicalCategory
chosen
Indicates the classification of something according to a particular theological type, tradition, or doctrinal category.
-
B.
typeOfTheology
Indicates the specific theological category, tradition, or system that characterizes a given religious belief, doctrine, or discourse.
-
C.
theologicalFocus
Indicates that something is primarily concerned with, centered on, or directed toward theological themes, questions, or doctrines.
-
D.
theologicalField
Indicates that something pertains to or is categorized within a specific area or branch of theology.
-
E.
theologicalBelief
Indicates that one entity holds or endorses a specific religious or theological doctrine, view, or set of beliefs about the divine or spiritual matters.
- 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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6c10eaccc819085320fffbb0aeceb |
completed | April 21, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c044d1108190b2b5d25de23f6401 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:09 p.m.