Triple
T4760482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leningrad Codex |
E105685
|
entity |
| Predicate | statusComparedToAleppoCodex |
P58362
|
FINISHED |
| Object | oldest complete manuscript while Aleppo Codex is older but partially lost |
—
|
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: oldest complete manuscript while Aleppo Codex is older but partially lost | Statement: [Leningrad Codex, statusComparedToAleppoCodex, oldest complete manuscript while Aleppo Codex is older but partially lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusComparedToAleppoCodex Context triple: [Leningrad Codex, statusComparedToAleppoCodex, oldest complete manuscript while Aleppo Codex is older but partially lost]
-
A.
textSourceApocrypha
Indicates that the referenced text originates from or is classified as apocryphal writings.
-
B.
textualBasisNewTestament
Indicates that something is based on, derived from, or justified by a text from the New Testament.
-
C.
numberInBiblicalText
Indicates that a specific number appears within, or is referenced by, a given passage or unit of biblical text.
-
D.
textBasisNewTestament
Indicates that a text is based on, derived from, or grounded in the New Testament.
-
E.
inChristianCanonOrder
Indicates that the entities are arranged according to the sequence used in the Christian biblical canon.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650dc7fc81909b483ef3c456ae0d |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd631328fc81909b28ae0a2a3ed9bb |
completed | March 20, 2026, 3:09 p.m. |
Created at: March 20, 2026, 1:20 p.m.