Triple
T898894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apocrypha (in early editions) |
E19403
|
entity |
| Predicate | positionInBible |
P21149
|
FINISHED |
| Object | between Old Testament and New Testament |
—
|
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: between Old Testament and New Testament | Statement: [Apocrypha (in early editions), positionInBible, between Old Testament and New Testament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInBible Context triple: [Apocrypha (in early editions), positionInBible, between Old Testament and New Testament]
-
A.
positionInHebrewBible
Indicates the ordinal position that something occupies within the canonical sequence of books or passages in the Hebrew Bible.
-
B.
positionAmongGospels
Indicates the numerical order or placement of a given gospel within the sequence of all gospels.
-
C.
positionInTanakh
Indicates the relative location or ordering of a text or passage within the canonical structure of the Tanakh.
-
D.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
-
E.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad4162848190aa2787b2fa3e6575 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4abb157d08190a7d7281eb3f1b788 |
completed | March 1, 2026, 9:12 p.m. |
Created at: March 1, 2026, 7:39 p.m.