Triple
T4760455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leningrad Codex |
E105685
|
entity |
| Predicate | completeness |
P26754
|
FINISHED |
| Object | complete Hebrew Bible |
—
|
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: complete Hebrew Bible | Statement: [Leningrad Codex, completeness, complete Hebrew Bible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completeness Context triple: [Leningrad Codex, completeness, complete Hebrew Bible]
-
A.
isIncompletenessSubjectTo
Indicates that an incompleteness, deficiency, or lack in something is governed, constrained, or determined by a particular condition, rule, or authority.
-
B.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
-
C.
closureCompleted
Indicates that a previously initiated closure process or shutdown has been fully and successfully completed.
-
D.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
E.
inscriptionCompleteness
chosen
Indicates how fully or partially an inscription is preserved or recorded in relation to its original state.
- 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_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. |
Created at: March 20, 2026, 1:20 p.m.