Triple
T34369113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Descendants of Abraham |
E882102
|
entity |
| Predicate | includesCovenantLine |
P205412
|
FINISHED |
| Object | children of Israel |
E83090
|
NE 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: children of Israel | Statement: [Descendants of Abraham, includesCovenantLine, children of Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCovenantLine Context triple: [Descendants of Abraham, includesCovenantLine, children of Israel]
-
A.
hasCovenants
Indicates that one entity is bound by or associated with formal covenants, agreements, or binding promises in relation to another entity or context.
-
B.
covenantWith
Indicates a formal, binding agreement or promise established between two or more parties.
-
C.
inscriptionIncludesLine
Indicates that an inscription contains a specific line of text as one of its components.
-
D.
covenantStatus
Indicates the current state or condition of a covenant or binding agreement between parties.
-
E.
lineIncludes
Indicates that a specific line (such as a text line, code line, or route segment) contains or encompasses a given element or component.
- F. None of above. chosen
Provenance (5 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3704ae23b881908d28cc58c0b8dd64 |
completed | June 20, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:58 a.m.