Triple
T34513621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mormonism |
E886089
|
entity |
| Predicate | claimsToRestore |
P32091
|
FINISHED |
| Object | original church of Jesus Christ |
—
|
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: original church of Jesus Christ | Statement: [Mormonism, claimsToRestore, original church of Jesus Christ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsToRestore Context triple: [Mormonism, claimsToRestore, original church of Jesus Christ]
-
A.
claimsToBe
chosen
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
B.
claimsToMark
Indicates that one entity asserts or alleges that it has marked, labeled, or designated another entity in some specified way.
-
C.
claimsToModify
Indicates that one entity asserts it can change, alter, or adjust another entity or its properties.
-
D.
claimsToEliminate
Indicates that one entity asserts it will remove, eradicate, or put an end to another entity or condition.
-
E.
claimsToContinue
Indicates that one entity asserts or promises that an action, state, or relationship will persist into the future.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 2:01 a.m.