Triple
T23722684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannah, mother of the prophet Samuel |
E586185
|
entity |
| Predicate | husbandHasAnotherWife |
P133396
|
FINISHED |
| Object | Peninnah |
—
|
NE NERFINISHED |
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: Peninnah | Statement: [Hannah, mother of the prophet Samuel, husbandHasAnotherWife, Peninnah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: husbandHasAnotherWife Context triple: [Hannah, mother of the prophet Samuel, husbandHasAnotherWife, Peninnah]
-
A.
hasAnotherWife
chosen
Indicates that a person is married to more than one wife, specifying the existence of an additional wife beyond the first.
-
B.
wasCheatedOnBy
Indicates that one entity was the victim of infidelity committed by another entity in a romantic or committed relationship.
-
C.
exSpouse
Indicates that two people were formerly married to each other but are no longer spouses.
-
D.
spouseAccusation
Indicates that one spouse has accused the other spouse of some wrongdoing, misconduct, or blameworthy action.
-
E.
spouseLaterMarriedBy
Indicates that one’s spouse subsequently entered into a later marriage with another partner.
- 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b912a7548190afcfa03dd9adc47e |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:04 p.m.