Triple
T207598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New International Version |
E4641
|
entity |
| Predicate | containsDeuterocanonicalBooks |
P2306
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [New International Version, containsDeuterocanonicalBooks, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsDeuterocanonicalBooks Context triple: [New International Version, containsDeuterocanonicalBooks, no]
-
A.
excludesDeuterocanonicalBooksIn
chosen
Indicates that a canon, edition, or tradition omits the Deuterocanonical books from a specified scriptural collection or corpus.
-
B.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
C.
hasLanguageOfScripture
Indicates that an entity’s scriptural or sacred texts are written or expressed in a specified language.
-
D.
hasLiturgicalBook
Indicates that one entity possesses, uses, or is associated with a specific liturgical book in a religious or worship context.
-
E.
hasViewOnScripture
Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.