Triple
T30745848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tablets of the Divine Plan |
E782813
|
entity |
| Predicate | religiousFigureAuthor |
P95657
|
FINISHED |
| Object | ʻAbdu'l‑Bahá, son of Baháʼu'lláh |
—
|
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: ʻAbdu'l‑Bahá, son of Baháʼu'lláh | Statement: [Tablets of the Divine Plan, religiousFigureAuthor, ʻAbdu'l‑Bahá, son of Baháʼu'lláh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousFigureAuthor Context triple: [Tablets of the Divine Plan, religiousFigureAuthor, ʻAbdu'l‑Bahá, son of Baháʼu'lláh]
-
A.
religiousFigure
Indicates that one entity is recognized or designated as a religious leader, authority, or sacred person in relation to another entity.
-
B.
religiousFigureType
Indicates the specific role or category of a person recognized as a religious figure (e.g., priest, monk, prophet) within a religious context.
-
C.
writtenByClergyOrTheologian
chosen
Indicates that the work or text was authored by a member of the clergy or a professional theologian.
-
D.
religiousFigureBornHere
Indicates that a notable religious figure was born at this location.
-
E.
authorsReligion
Indicates the religious affiliation or belief system associated with an author.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: April 29, 2026, 8:38 p.m.