Triple
T9400074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaredites |
E226443
|
entity |
| Predicate | covenantTheme |
P59157
|
FINISHED |
| Object | blessings in the promised land conditioned on righteousness |
—
|
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: blessings in the promised land conditioned on righteousness | Statement: [Jaredites, covenantTheme, blessings in the promised land conditioned on righteousness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: covenantTheme Context triple: [Jaredites, covenantTheme, blessings in the promised land conditioned on righteousness]
-
A.
covenantalTheme
chosen
Indicates a recurring, binding relational pattern or motif structured like a covenantal agreement between parties.
-
B.
covenantView
Indicates a relationship where one party observes, understands, or interprets the terms, conditions, or implications of a covenant or binding agreement.
-
C.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
D.
signOfCovenant
Indicates that something serves as a visible or symbolic marker confirming the existence and terms of a covenant between parties.
-
E.
covenantAdopted
Indicates that a covenant has been formally accepted and put into effect by the relevant party or parties.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5156b9588190bafb6b1c3ee3c0ed |
completed | April 1, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:46 p.m.