Triple
T14629799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judith daughter of Beeri the Hittite |
E343448
|
entity |
| Predicate | spouseCountContext |
P58368
|
FINISHED |
| Object | one of the wives of Esau |
—
|
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: one of the wives of Esau | Statement: [Judith daughter of Beeri the Hittite, spouseCountContext, one of the wives of Esau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseCountContext Context triple: [Judith daughter of Beeri the Hittite, spouseCountContext, one of the wives of Esau]
-
A.
spouseCount
chosen
Indicates the number of spouses an entity has.
-
B.
spouseRelationshipContext
Indicates a marital relationship context between two entities, specifying that they are spouses or partners in a recognized marriage-like union.
-
C.
hasNumberOfChildrenWithSpouse
Indicates the count of children that an individual has specifically with a given spouse.
-
D.
spouseInFamily
Indicates that a person is a spouse (married partner) within the context of a specific family unit.
-
E.
spouseType
Indicates the specific role or category of a person within a spousal relationship (e.g., husband, wife, 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4a912248190a3df7f821395c776 |
completed | April 14, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.