Triple
T3211058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simeon |
E67279
|
entity |
| Predicate | covenantalStatus |
P36140
|
FINISHED |
| Object | heir of Abrahamic covenant |
—
|
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: heir of Abrahamic covenant | Statement: [Simeon, covenantalStatus, heir of Abrahamic covenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: covenantalStatus Context triple: [Simeon, covenantalStatus, heir of Abrahamic covenant]
-
A.
covenantalStatusInBible
chosen
Indicates the type or state of covenantal relationship an entity holds within the context of the Bible.
-
B.
covenantAdopted
Indicates that a covenant has been formally accepted and put into effect by the relevant party or parties.
-
C.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
D.
religiousStatus
Indicates the religious affiliation, role, or standing that an entity holds within a religious context.
-
E.
signOfCovenant
Indicates that something serves as a visible or symbolic marker confirming the existence and terms of a covenant between 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaab886c48190b72e36d0ac855ffe |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.