Triple
T15003066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book VI (Divine Institutes) |
E374139
|
entity |
| Predicate | isApologyFor |
P116314
|
FINISHED |
| Object | Christian faith |
—
|
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: Christian faith | Statement: [Book VI (Divine Institutes), isApologyFor, Christian faith]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isApologyFor Context triple: [Book VI (Divine Institutes), isApologyFor, Christian faith]
-
A.
apologizedFor
Indicates that one entity expressed regret or remorse to another entity specifically about a particular action, event, or wrongdoing.
-
B.
apologyIssued
Indicates that one entity has expressed regret or remorse to another entity for a perceived wrong, mistake, or offense.
-
C.
apologyIssuedBy
Indicates that an apology has been made by a specific entity as the source or initiator of that apology.
-
D.
containsExplicitApology
Indicates that one entity includes a direct and unambiguous expression of apology toward another entity.
-
E.
apologeticFunction
Indicates that one entity expresses regret or remorse to another, acknowledging fault or seeking forgiveness for an action or outcome.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7312ae48190bdaf91ecced6657e |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:54 a.m.