Triple
T13681633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TEV |
E328016
|
entity |
| Predicate | firstNewTestamentPublication |
P10014
|
FINISHED |
| Object | 1966 |
—
|
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: 1966 | Statement: [TEV, firstNewTestamentPublication, 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstNewTestamentPublication Context triple: [TEV, firstNewTestamentPublication, 1966]
-
A.
firstNewTestamentEditionYear
Indicates the year in which the first edition of the New Testament associated with an entity was published.
-
B.
newTestamentFirstPublishedYear
chosen
Indicates the year in which the New Testament was first published or made publicly available.
-
C.
newTestamentPublishedIn
Indicates that a specific edition or version of the New Testament was published in a particular place, time, or publication context.
-
D.
firstCompleteBiblePublicationDate
Indicates the date on which the first complete edition of the Bible associated with an entity was published.
-
E.
OldTestamentFirstPublished
Indicates that the Old Testament was first made publicly available in written or printed form at a particular time or by a particular edition.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.