Triple
T4935585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abimelech |
E110803
|
entity |
| Predicate | motherInstanceOf |
P60483
|
FINISHED |
| Object | concubine |
—
|
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: concubine | Statement: [Abimelech, motherInstanceOf, concubine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motherInstanceOf Context triple: [Abimelech, motherInstanceOf, concubine]
-
A.
motherIs
Indicates that one entity is the mother (biological or adoptive) of another entity.
-
B.
motherFrom
Indicates that one entity is the mother (biological or adoptive) of another entity, specifying a maternal parent-child relationship from the mother to the child.
-
C.
motherIsMemberOf
Indicates that the person identified as the mother belongs to or is part of a specified group, organization, or collection.
-
D.
isMotherOf
Indicates that one entity is the female parent who has given birth to or legally/ socially parents the other entity.
-
E.
ancestorMother
Indicates that one entity is a female ancestor (mother, grandmother, etc.) of another entity in a family lineage.
- F. None of above. chosen
Provenance (4 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd706825188190b854dca5ca2f9db6 |
completed | March 20, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6ff731188190a9903602122d4ff9 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:30 p.m.