Triple
T8896240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Ephraemi Rescriptus |
E211810
|
entity |
| Predicate | GregoryAlandNumber |
P85108
|
FINISHED |
| Object | 03 |
—
|
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: 03 | Statement: [Codex Ephraemi Rescriptus, GregoryAlandNumber, 03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GregoryAlandNumber Context triple: [Codex Ephraemi Rescriptus, GregoryAlandNumber, 03]
-
A.
numberingInSeptuagintVulgate
Indicates that the entity uses the chapter or verse numbering system as found in the Septuagint and Vulgate traditions.
-
B.
numberInBiblicalText
Indicates that a specific number appears within, or is referenced by, a given passage or unit of biblical text.
-
C.
numberOfCanonicalGospels
Indicates the count of canonical gospels associated with a given religious tradition or context.
-
D.
inChristianCanonOrder
Indicates that the entities are arranged according to the sequence used in the Christian biblical canon.
-
E.
hasRahlfsNumber
Indicates that an entity (typically a Septuagint manuscript or text unit) is associated with a specific Rahlfs catalog number used to identify it.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61bfec0881908e4ef5b7f0e6b542 |
completed | April 1, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2bfb38819083d5eb1af8ccf4d6 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cffe8ec819084c12770fe0578f2 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:54 p.m.