Triple
T34414557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Doctrine of Redemption |
E883364
|
entity |
| Predicate | plannedForm |
P164026
|
FINISHED |
| Object | volume of systematic 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: volume of systematic theology | Statement: [The Doctrine of Redemption, plannedForm, volume of systematic theology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedForm Context triple: [The Doctrine of Redemption, plannedForm, volume of systematic theology]
-
A.
formationPlannedFor
Indicates that a specific formation or organizational structure is scheduled or intended to be created for a given entity or context.
-
B.
envisionedForm
chosen
Indicates that one entity is the mental image, design, or conceptual form that another entity has imagined or planned.
-
C.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
D.
projectedForm
Indicates that one entity is a representation or projection of another entity into a different form, space, or perspective.
-
E.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
- 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_69f349c2e3b88190a67834eb5bcffeaf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 1:59 a.m.