Triple
T4761285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribe of Ephraim |
E105702
|
entity |
| Predicate | genealogicalGroup |
P35417
|
FINISHED |
| Object | children of Joseph |
—
|
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: children of Joseph | Statement: [Tribe of Ephraim, genealogicalGroup, children of Joseph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genealogicalGroup Context triple: [Tribe of Ephraim, genealogicalGroup, children of Joseph]
-
A.
ancestralGroup
chosen
Indicates that one entity is a broader ancestral lineage, population, or group from which the other entity descends or originates.
-
B.
genealogicalFunction
Indicates a genealogical relationship or role that one entity holds in relation to another within a family or ancestry structure.
-
C.
genealogicalLine
Indicates a genealogical relationship connecting individuals through lines of descent or ancestry.
-
D.
familyGroup
Indicates that multiple entities are related to each other as members of the same family unit or household.
-
E.
genealogicalDescription
Indicates a textual description that explains the genealogical relationships or lineage connections among entities.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.