Triple
T35788407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head of the Bahá'í Faith |
E1034622
|
entity |
| Predicate | doctrineRelatedToOffice |
P14928
|
FINISHED |
| Object | Bahá'í Covenant |
—
|
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: Bahá'í Covenant | Statement: [Head of the Bahá'í Faith, doctrineRelatedToOffice, Bahá'í Covenant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrineRelatedToOffice Context triple: [Head of the Bahá'í Faith, doctrineRelatedToOffice, Bahá'í Covenant]
-
A.
relatesToOffice
chosen
Indicates that one entity has a connection, association, or relevance to an office, its functions, or its environment.
-
B.
subjectOffice
Indicates the office or official position held by the subject in relation to another entity or context.
-
C.
definesOfficeOf
Indicates that one entity specifies or establishes the official role, position, or office associated with another entity.
-
D.
givenByOffice
Indicates that something (such as a document, decision, or service) is provided or issued by a specific office or official authority.
-
E.
hasAssociatedOffice
Indicates that an entity is linked to or connected with a particular office in an official or functional capacity.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a22c18788190812092e3eadd4711 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.