Triple
T34513656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mormonism |
E886089
|
entity |
| Predicate | familyDoctrine |
P190519
|
FINISHED |
| Object | eternal families |
—
|
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: eternal families | Statement: [Mormonism, familyDoctrine, eternal families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyDoctrine Context triple: [Mormonism, familyDoctrine, eternal families]
-
A.
familyAuthority
Indicates that one entity holds recognized decision-making power or control over another within a family or household context.
-
B.
familyDivision
Indicates a relationship where a family is split into distinct parts or groups, often due to conflict, separation, or differing affiliations.
-
C.
mainFamilyLaw
Indicates that one entity serves as the primary governing family-law framework, rule, or authority for another entity (such as a case, jurisdiction, or legal matter).
-
D.
cultFamily
Indicates that one entity is a family member of another within the context of a cult or cult-like group.
-
E.
family
Indicates a familial relationship or connection between entities, such as being related by blood, marriage, or adoption.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: May 1, 2026, 2:01 a.m.