Triple
T17683673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan son of Jacob |
E440832
|
entity |
| Predicate | birthOrderAmongSonsOfJacobByMother |
P128563
|
FINISHED |
| Object | first son of Bilhah |
—
|
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: first son of Bilhah | Statement: [Dan son of Jacob, birthOrderAmongSonsOfJacobByMother, first son of Bilhah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthOrderAmongSonsOfJacobByMother Context triple: [Dan son of Jacob, birthOrderAmongSonsOfJacobByMother, first son of Bilhah]
-
A.
birthOrderAmongDavidSons
Indicates the relative position of a son in the sequence of David’s sons, specifying his numerical order of birth among them.
-
B.
descendantsCountInGenesis46
Indicates the number of a person’s descendants who are listed in the genealogical record of Genesis chapter 46.
-
C.
gaveBirthTo
Indicates that one entity is the biological parent who delivered another entity as offspring.
-
D.
numberOfSons
Indicates the count of male offspring that an entity has.
-
E.
listedAsSonOf
Indicates that one entity is recorded or designated as the son (male child) of another entity.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704626308190bbdd98d27beb3f24 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:02 a.m.