Triple
T36711306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | יְהוֹצָדָק |
E906799
|
entity |
| Predicate | hasGenealogicalPosition |
P193375
|
FINISHED |
| Object | descendant of Aaron through Eleazar |
—
|
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: descendant of Aaron through Eleazar | Statement: [יְהוֹצָדָק, hasGenealogicalPosition, descendant of Aaron through Eleazar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenealogicalPosition Context triple: [יְהוֹצָדָק, hasGenealogicalPosition, descendant of Aaron through Eleazar]
-
A.
hasGenealogicalRelation
Indicates that there exists a family or ancestry-based relationship (such as parent, child, sibling, or more distant kinship) between the related entities.
-
B.
hasGenealogy
Indicates that one entity possesses or is associated with the genealogical record, lineage, or ancestry information of another entity.
-
C.
hasGenealogicalSignificance
Indicates that something holds importance or relevance within a genealogical or family-lineage context.
-
D.
hasGenealogicalType
chosen
Indicates that one entity is associated with another through a specified genealogical relationship type (e.g., ancestor, descendant, sibling).
-
E.
hasGenealogicalInterest
Indicates a relationship in which one entity has a research, documentation, or personal interest in the family history or lineage 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
Created at: May 3, 2026, 4:12 p.m.