Triple
T35977851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosh Galut |
E1040471
|
entity |
| Predicate | religiousLegitimization |
P129811
|
FINISHED |
| Object | Davidic genealogy |
—
|
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: Davidic genealogy | Statement: [Rosh Galut, religiousLegitimization, Davidic genealogy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousLegitimization Context triple: [Rosh Galut, religiousLegitimization, Davidic genealogy]
-
A.
religiousLegitimation
chosen
Indicates that something is justified, authorized, or validated by reference to religious beliefs, doctrines, or institutions.
-
B.
religiousClaim
Indicates that an entity asserts, expresses, or is associated with a statement or belief grounded in religion or spiritual doctrine.
-
C.
religiousElement
Indicates that something is a component, aspect, or feature associated with a religion or religious practice.
-
D.
religiousTextStatus
Indicates the status or role that a text holds within a religious tradition, such as whether it is considered sacred, canonical, apocryphal, or otherwise classified.
-
E.
religiousCanon
Indicates that something is formally recognized as part of an established body of authoritative religious texts or doctrine.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:07 p.m.