Triple
T19074450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gospel of Judas |
E466868
|
entity |
| Predicate | acceptedInNewTestamentCanon |
P108450
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Gospel of Judas, acceptedInNewTestamentCanon, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptedInNewTestamentCanon Context triple: [Gospel of Judas, acceptedInNewTestamentCanon, no]
-
A.
includedInNewTestamentCanon
chosen
Indicates that something is recognized as part of the officially accepted collection of writings in the New Testament canon.
-
B.
sharesNewTestamentCanonWith
Indicates that two entities recognize and use the same set of New Testament canonical books.
-
C.
scripturalCanonStatus
Indicates whether and how a text is recognized as part of an authoritative scriptural canon within a given religious or doctrinal tradition.
-
D.
textBasisNewTestament
Indicates that a text is based on, derived from, or grounded in the New Testament.
-
E.
earlyNewTestamentOmissions
Indicates that a referenced element, passage, or feature is absent from the earliest New Testament manuscripts or textual witnesses.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e2ccbc8190bf5a2da915c81a03 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.