Triple
T19289565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elohim |
E482403
|
entity |
| Predicate | roleInGenesis1 |
P27433
|
FINISHED |
| Object | creator of heavens and earth |
—
|
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: creator of heavens and earth | Statement: [Elohim, roleInGenesis1, creator of heavens and earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInGenesis1 Context triple: [Elohim, roleInGenesis1, creator of heavens and earth]
-
A.
creatorOfInhabitants
Indicates that an entity is the creator or originator of the beings or inhabitants of another entity (such as a place, world, or domain).
-
B.
biblicalFigureRole
chosen
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
C.
roleInJoshua
Indicates that an entity holds a specific role or function within the context of the Book of Joshua or its narrative events.
-
D.
roleInOrigin
Indicates that an entity holds or held a specific role, function, or position within the context of its origin or source.
-
E.
roleInEschatology
Indicates the role or function an entity is believed to have within doctrines, narratives, or expectations about the end times or ultimate destiny of the world.
- 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.