Triple
T24177116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ephraim son of Joseph |
E599312
|
entity |
| Predicate | birthOrderRelativeToManasseh |
P20593
|
FINISHED |
| Object | younger |
—
|
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: younger | Statement: [Ephraim son of Joseph, birthOrderRelativeToManasseh, younger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birthOrderRelativeToManasseh Context triple: [Ephraim son of Joseph, birthOrderRelativeToManasseh, younger]
-
A.
birthOrderAmongSonsOfJacobByMother
Indicates the relative birth position of a son among Jacob’s sons born to the same mother.
-
B.
positionInFamilyBirthOrder
chosen
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
C.
descendantsCountInGenesis46
Indicates the number of a person’s descendants who are listed in the genealogical record of Genesis chapter 46.
-
D.
birthOrderAmongDavidSons
Indicates the relative position of a son in the sequence of David’s sons, specifying his numerical order of birth among them.
-
E.
positionInPatriarchs
Indicates the specific rank or placement an individual holds within a defined lineage or hierarchy of patriarchs.
- 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:34 p.m.