Triple
T4768645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abrahamic covenant |
E105871
|
entity |
| Predicate | covenantForm |
P58664
|
FINISHED |
| Object | divine promise |
—
|
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: divine promise | Statement: [Abrahamic covenant, covenantForm, divine promise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: covenantForm Context triple: [Abrahamic covenant, covenantForm, divine promise]
-
A.
covenantWith
Indicates a formal, binding agreement or promise established between two or more 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.
covenantAdopted
Indicates that a covenant has been formally accepted and put into effect by the relevant party or parties.
-
D.
signOfCovenant
Indicates that something serves as a visible or symbolic marker confirming the existence and terms of a covenant between parties.
-
E.
covenantLocation
Indicates the place or setting where a covenant or formal agreement is established, held, or applies.
- F. None of above. chosen
Provenance (4 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6537eb80819096e0ae906c59d605 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6508e218819086a36236cfa4a249 |
completed | March 20, 2026, 3:17 p.m. |
Created at: March 20, 2026, 1:21 p.m.