Triple
T9504348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulekites |
E229223
|
entity |
| Predicate | religiousLeadersAfterUnion |
P88427
|
FINISHED |
| Object | Nephite prophets |
—
|
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: Nephite prophets | Statement: [Mulekites, religiousLeadersAfterUnion, Nephite prophets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousLeadersAfterUnion Context triple: [Mulekites, religiousLeadersAfterUnion, Nephite prophets]
-
A.
religiousLeadershipStart
Indicates the point in time when an entity begins serving in a religious leadership role or office.
-
B.
religiousLeadershipSupport
Indicates that one entity provides backing, endorsement, or assistance to another in the context of religious leadership or authority.
-
C.
clergy
Indicates that an entity serves in an official religious or spiritual leadership role within an organized faith or religious institution.
-
D.
religiousFigure
Indicates that one entity is recognized or designated as a religious leader, authority, or sacred person in relation to another entity.
-
E.
clergyComposition
Indicates the makeup or distribution of different types of clergy within a religious organization or context.
- 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_69ca847611c48190a28c028644198c75 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9840148081908df237f212b62e67 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca567ca448190bf4bcce8ce7dd54f |
completed | April 1, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:57 p.m.