Triple
T24241975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asher son of Jacob |
E603253
|
entity |
| Predicate | birthOrderAmongSonsOfJacobWithZilpah |
P128563
|
FINISHED |
| Object | second son of Zilpah |
—
|
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: second son of Zilpah | Statement: [Asher son of Jacob, birthOrderAmongSonsOfJacobWithZilpah, second son of Zilpah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthOrderAmongSonsOfJacobWithZilpah Context triple: [Asher son of Jacob, birthOrderAmongSonsOfJacobWithZilpah, second son of Zilpah]
-
A.
birthOrderAmongSonsOfJacobByMother
chosen
Indicates the relative birth position of a son among Jacob’s sons born to the same mother.
-
B.
birthOrderAmongDavidSons
Indicates the relative position of a son in the sequence of David’s sons, specifying his numerical order of birth among them.
-
C.
numberOfSons
Indicates the count of male offspring that an entity has.
-
D.
positionInFamilyBirthOrder
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
E.
listedAsSonOf
Indicates that one entity is recorded or designated as the son (male child) of 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_69e2953f631c819097cbb421046bd417 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28aa04fe08190922d6abde695571a |
completed | April 29, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:03 a.m.