Triple
T331633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | God |
E6636
|
entity |
| Predicate | keyNarrative |
P6847
|
FINISHED |
| Object | creation of the world in Genesis |
—
|
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: creation of the world in Genesis | Statement: [God, keyNarrative, creation of the world in Genesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyNarrative Context triple: [God, keyNarrative, creation of the world in Genesis]
-
A.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
B.
containsNarrativeOf
chosen
Indicates that one entity includes or presents the story, account, or narrative content of another entity.
-
C.
keyPassage
Indicates that a specific passage or excerpt is identified as especially important, central, or representative within a larger text or discourse.
-
D.
keyFeature
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
E.
narrativeStyle
Indicates how a narrative is told, such as the point of view, tone, and structural approach used to present a story or account.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eaafd1a48190a6d001af3c2a5318 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94c6d8881908239d3788c018adf |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.