Triple
T934745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Alexandrinus |
E20169
|
entity |
| Predicate | textTypeNewTestament |
P6836
|
FINISHED |
| Object | Byzantine text-type (Gospels) |
—
|
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: Byzantine text-type (Gospels) | Statement: [Codex Alexandrinus, textTypeNewTestament, Byzantine text-type (Gospels)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textTypeNewTestament Context triple: [Codex Alexandrinus, textTypeNewTestament, Byzantine text-type (Gospels)]
-
A.
textBasisNewTestament
Indicates that a text is based on, derived from, or grounded in the New Testament.
-
B.
textualBasisNewTestament
Indicates that something is based on, derived from, or justified by a text from the New Testament.
-
C.
scriptureType
chosen
Indicates the classification or category of a scripture in relation to its type or genre.
-
D.
bookNumberInNewTestament
Indicates the numerical position a specific book occupies within the sequence of books in the New Testament.
-
E.
textSourceApocrypha
Indicates that the referenced text originates from or is classified as apocryphal writings.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b363ea5c819098ec1d87f785bad4 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29b245c8190b143f28b77fede3c |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.