Triple
T19909408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epistle to Diognetus |
E478504
|
entity |
| Predicate | modernClassification |
P44056
|
FINISHED |
| Object | patristic literature |
—
|
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: patristic literature | Statement: [Epistle to Diognetus, modernClassification, patristic literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernClassification Context triple: [Epistle to Diognetus, modernClassification, patristic literature]
-
A.
eraClassification
chosen
Indicates the historical era or time period into which an entity is categorized or classified.
-
B.
statusInModernBiology
Indicates the recognized role, classification, or relevance that something holds within the framework of contemporary biological science.
-
C.
classificationSystem
Indicates a relationship where an entity is organized or categorized according to a particular classification scheme or taxonomy.
-
D.
taxonType
Indicates the biological or taxonomic rank/category that characterizes a given taxon.
-
E.
taxonCircumscription
Indicates the taxonomic scope or boundary within which a particular taxon is defined or delimited in a classification.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6598e7d988190b8759100a147f2c1 |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.