Triple
T19289564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elohim |
E482403
|
entity |
| Predicate | firstBiblicalOccurrence |
P3921
|
FINISHED |
| Object | Genesis 1:1 |
—
|
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: Genesis 1:1 | Statement: [Elohim, firstBiblicalOccurrence, Genesis 1:1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBiblicalOccurrence Context triple: [Elohim, firstBiblicalOccurrence, Genesis 1:1]
-
A.
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.
-
B.
firstClearlyAttestedIn
chosen
Indicates the earliest known point in time or source where something is clearly documented or evidenced.
-
C.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
D.
firstBibleTranslationYear
Indicates the year in which the first translation of the Bible into a given language or for a given context was completed or published.
-
E.
hasPrimaryBiblicalText
Indicates that one entity is associated with another entity that serves as its main or authoritative biblical text.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc050a888190ac204d1e736200c5 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.