Triple
T13681634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TEV |
E328016
|
entity |
| Predicate | completeBiblePublication |
P11530
|
FINISHED |
| Object | 1976 |
—
|
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: 1976 | Statement: [TEV, completeBiblePublication, 1976]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completeBiblePublication Context triple: [TEV, completeBiblePublication, 1976]
-
A.
firstCompleteBiblePublicationDate
chosen
Indicates the date on which the first complete edition of the Bible associated with an entity was published.
-
B.
oldTestamentPublishedIn
Indicates that a specific edition or version of the Old Testament was published in a particular place or medium.
-
C.
scriptureTypeTranslated
Indicates that a scripture or sacred text has been translated into a particular type, version, or format.
-
D.
scriptureType
Indicates the classification or category of a scripture in relation to its type or genre.
-
E.
firstCompleteBibleTranslationBy
Indicates that an entity is the first person or group to have completed a full translation of a particular Bible into a given language or form.
- 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.