Triple
T19373340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quadratus of Athens |
E484600
|
entity |
| Predicate | apologyType |
P55701
|
FINISHED |
| Object | Christian apology |
—
|
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 apology | Statement: [Quadratus of Athens, apologyType, Christian apology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apologyType Context triple: [Quadratus of Athens, apologyType, Christian apology]
-
A.
typeOfApology
chosen
Indicates that one entity specifies the particular kind or category of apology expressed in relation to another entity.
-
B.
apologyIssued
Indicates that one entity has expressed regret or remorse to another entity for a perceived wrong, mistake, or offense.
-
C.
apologizedFor
Indicates that one entity expressed regret or remorse to another entity specifically about a particular action, event, or wrongdoing.
-
D.
apologyIssuedBy
Indicates that an apology has been made by a specific entity as the source or initiator of that apology.
-
E.
apologeticMethod
Indicates the manner or approach by which an apology is expressed or delivered from one entity to another.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61a59f8cc8190b314cba95c25f2a0 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.