Triple
T9962830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Claromontanus (D 06) |
E195609
|
entity |
| Predicate | gregoryAlandNumber |
P85108
|
FINISHED |
| Object | D 06 |
—
|
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: D 06 | Statement: [Codex Claromontanus (D 06), gregoryAlandNumber, D 06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gregoryAlandNumber Context triple: [Codex Claromontanus (D 06), gregoryAlandNumber, D 06]
-
A.
GregoryAlandNumber
chosen
Indicates the standardized catalog number assigned to a New Testament manuscript in the Gregory-Aland classification system.
-
B.
numberingInSeptuagintVulgate
Indicates that the entity uses the chapter or verse numbering system as found in the Septuagint and Vulgate traditions.
-
C.
scripturalNumberingSystem
Indicates a relationship where a particular numbering system is used to organize, reference, or index passages within a scriptural text.
-
D.
hasRahlfsNumber
Indicates that an entity (typically a Septuagint manuscript or text unit) is associated with a specific Rahlfs catalog number used to identify it.
-
E.
numberInBiblicalText
Indicates that a specific number appears within, or is referenced by, a given passage or unit of biblical text.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb718cd588190a4aac48220deddec |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.