Triple
T30747048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covenant in the Bahá'í Faith |
E782840
|
entity |
| Predicate | CenterOfCovenant |
P170091
|
FINISHED |
| Object | ‘Abdu’l‑Bahá |
—
|
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á | Statement: [Covenant in the Bahá'í Faith, CenterOfCovenant, ‘Abdu’l‑Bahá]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CenterOfCovenant Context triple: [Covenant in the Bahá'í Faith, CenterOfCovenant, ‘Abdu’l‑Bahá]
-
A.
covenantCommunity
Indicates a relationship in which entities are bound together by a shared covenant, forming a committed, mutually obligated community.
-
B.
covenantalTheme
Indicates a recurring, binding relational pattern or motif structured like a covenantal agreement between parties.
-
C.
signOfCovenant
Indicates that something serves as a visible or symbolic marker confirming the existence and terms of a covenant between parties.
-
D.
covenantLocation
Indicates the place or setting where a covenant or formal agreement is established, held, or applies.
-
E.
covenantAssociation
Indicates a formal, binding relationship or agreement that associates entities under shared obligations, promises, or terms.
- F. None of above. chosen
Provenance (4 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_69f68f6e3b888190b1983fccc3151aa6 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f68848ad348190a2fb6e841dcfdb7d |
completed | May 2, 2026, 11:27 p.m. |
Created at: April 29, 2026, 8:38 p.m.