Triple
T19928472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermas |
E478988
|
entity |
| Predicate | textReception |
P137867
|
FINISHED |
| Object | excluded from final New Testament canon |
—
|
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: excluded from final New Testament canon | Statement: [Hermas, textReception, excluded from final New Testament canon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textReception Context triple: [Hermas, textReception, excluded from final New Testament canon]
-
A.
textualTransmission
Indicates the transfer or communication of information through written or printed text from one source to another.
-
B.
textType
Indicates the classification of a text according to its type, format, or genre.
-
C.
receives
Indicates that one entity is the recipient of something (such as an object, message, or action) from another entity.
-
D.
textBy
Indicates that a given text or written content was authored or produced by a particular entity.
-
E.
initialReception
Indicates the nature or quality of the first response or reaction something receives when it is introduced or presented.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659cd4500819090363a4b7d6bf193 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:53 p.m.