Triple
T16432878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis 41 |
E399110
|
entity |
| Predicate | recordsMarriage |
P21096
|
FINISHED |
| Object | Joseph’s marriage to Asenath |
—
|
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: Joseph’s marriage to Asenath | Statement: [Genesis 41, recordsMarriage, Joseph’s marriage to Asenath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsMarriage Context triple: [Genesis 41, recordsMarriage, Joseph’s marriage to Asenath]
-
A.
marriageDocumentedIn
chosen
Indicates that a marriage event is recorded or evidenced in a specific document or source.
-
B.
numberOfMarriages
Indicates the total count of times an entity has been legally married.
-
C.
marriageFormedBy
Indicates that a marriage relationship was created or brought into existence by a specific event, action, or process.
-
D.
marriageDate
Indicates the specific date on which two entities entered into a marital relationship.
-
E.
marries
Indicates that one entity enters into a legally or socially recognized marital union with another entity.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32b9f2e8c81909c60b8fb78255e5f |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.