Triple
T430677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New King James Version |
E9704
|
entity |
| Predicate | NewTestamentFirstPublished |
P10014
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [New King James Version, NewTestamentFirstPublished, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NewTestamentFirstPublished Context triple: [New King James Version, NewTestamentFirstPublished, 1979]
-
A.
newTestamentFirstPublishedYear
chosen
Indicates the year in which the New Testament was first published or made publicly available.
-
B.
firstNewTestamentEditionYear
Indicates the year in which the first edition of the New Testament associated with an entity was published.
-
C.
textBasisNewTestament
Indicates that a text is based on, derived from, or grounded in the New Testament.
-
D.
firstCompleteBiblePublicationDate
Indicates the date on which the first complete edition of the Bible associated with an entity was published.
-
E.
bookNumberInNewTestament
Indicates the numerical position a specific book occupies within the sequence of books in the New Testament.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeef065c81908ed30528a61da132 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.