Triple
T3233283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinrich Bullinger |
E67791
|
entity |
| Predicate | doctrineDeveloped |
P27707
|
FINISHED |
| Object | covenant theology |
—
|
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: covenant theology | Statement: [Heinrich Bullinger, doctrineDeveloped, covenant theology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineDeveloped Context triple: [Heinrich Bullinger, doctrineDeveloped, covenant theology]
-
A.
developedDoctrine
chosen
Indicates that one entity created, formulated, or significantly advanced a particular doctrine or set of principles.
-
B.
doctrineExplainedBy
Indicates that an explanation or interpretation is provided for a particular doctrine by a specified source or agent.
-
C.
doctrineFocus
Indicates that a doctrine, teaching, or belief is primarily concerned with, centered on, or directed toward a particular subject or theme.
-
D.
appliedDoctrine
Indicates that a particular doctrine, principle, or rule has been put into practice or used in interpreting or deciding a specific case, situation, or context.
-
E.
developmentMethod
Indicates the process, technique, or approach used to create, build, or evolve something.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaedb718c8190aae12f763033713a |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:08 p.m.