Triple
T1321746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baptists |
E28232
|
entity |
| Predicate | theologyRange |
P5493
|
FINISHED |
| Object | from Calvinist to Arminian |
—
|
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: from Calvinist to Arminian | Statement: [Baptists, theologyRange, from Calvinist to Arminian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theologyRange Context triple: [Baptists, theologyRange, from Calvinist to Arminian]
-
A.
theologicalCategory
chosen
Indicates the classification of something according to a particular theological type, tradition, or doctrinal category.
-
B.
theologicalField
Indicates that something pertains to or is categorized within a specific area or branch of theology.
-
C.
theologicalFocus
Indicates that something is primarily concerned with, centered on, or directed toward theological themes, questions, or doctrines.
-
D.
theologicalContext
Indicates the religious or doctrinal framework, tradition, or set of beliefs within which something (such as a text, event, or concept) is interpreted or understood.
-
E.
theologicalConcept
Indicates that something is a religious or theological idea, doctrine, or principle within a belief system.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19932888190a3d45871e84f112e |
completed | March 1, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69a4beedb49c8190beb5b85cdda05013 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.