Triple
T32923238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rigdonite Church of Christ |
E842198
|
entity |
| Predicate | followsPropheticLineageClaimOf |
P4867
|
FINISHED |
| Object | Sidney Rigdon |
—
|
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: Sidney Rigdon | Statement: [Rigdonite Church of Christ, followsPropheticLineageClaimOf, Sidney Rigdon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsPropheticLineageClaimOf Context triple: [Rigdonite Church of Christ, followsPropheticLineageClaimOf, Sidney Rigdon]
-
A.
hasPriestlyLineage
Indicates that an entity descends from, or belongs to, a recognized priestly family or hereditary priestly line.
-
B.
lineageClaim
chosen
Indicates a claim or assertion that one entity is descended from, or belongs to the ancestral line of, another entity.
-
C.
recognizesAsRightfulSuccessorToProphet
Indicates that one entity acknowledges another as the legitimate and rightful successor to a prophet.
-
D.
divineLineage
Indicates that one entity is descended from, or originates from, a divine or god-like being.
-
E.
isSuccessorInTraditionTo
Indicates that one entity follows and continues the practices, ideas, or legacy of another within a particular tradition or lineage.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 1, 2026, 1:20 a.m.