Triple
T24324153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Joseph |
E613048
|
entity |
| Predicate | hasBiblicalFigureAsAncestor |
P8000
|
FINISHED |
| Object | Joseph |
—
|
NE NERFINISHED |
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: Joseph | Statement: [House of Joseph, hasBiblicalFigureAsAncestor, Joseph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiblicalFigureAsAncestor Context triple: [House of Joseph, hasBiblicalFigureAsAncestor, Joseph]
-
A.
hasPriestlyLineage
Indicates that an entity descends from, or belongs to, a recognized priestly family or hereditary priestly line.
-
B.
biblicalFigureFromClan
Indicates that a biblical figure belongs to, originates from, or is associated with a particular clan.
-
C.
foundingAncestor
chosen
Indicates that one entity is the original progenitor or earliest known ancestor from whom another entity or lineage descends.
-
D.
allegedAncestor
Indicates that one entity is claimed or suspected to be an ancestor of another, without confirming that the ancestral relationship is true.
-
E.
associatedBiblicalFigure
Indicates that one entity is linked or connected to a particular biblical figure, such as by reference, attribution, or traditional association.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292ae127881909ef1772278181ce3 |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:53 a.m.