Triple
T10023994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proslogion |
E200679
|
entity |
| Predicate | doctrineDiscussed |
P91768
|
FINISHED |
| Object | divine attributes |
—
|
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: divine attributes | Statement: [Proslogion, doctrineDiscussed, divine attributes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineDiscussed Context triple: [Proslogion, doctrineDiscussed, divine attributes]
-
A.
doctrineOf
Indicates a relationship where one entity is the doctrinal teaching, principle, or belief system associated with, derived from, or formally held by another entity.
-
B.
doctrineExplainedBy
Indicates that an explanation or interpretation is provided for a particular doctrine by a specified source or agent.
-
C.
doctrineClassification
Indicates how a particular doctrine is categorized or classified within a defined system of doctrinal types.
-
D.
doctrineHeld
Indicates that an agent adheres to, supports, or maintains a particular doctrine or set of principles.
-
E.
stateDoctrine
Indicates that a state or government officially endorses, promotes, or is guided by a particular doctrine, ideology, or set of principles.
- F. None of above. chosen
Provenance (4 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd7c75548190aa604d90d63dc111 |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:53 p.m.