Triple
T30876255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anti-Nephi-Lehies |
E786481
|
entity |
| Predicate | descendantsCovenant |
P155596
|
FINISHED |
| Object | mothers had covenanted not to fight |
—
|
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: mothers had covenanted not to fight | Statement: [Anti-Nephi-Lehies, descendantsCovenant, mothers had covenanted not to fight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: descendantsCovenant Context triple: [Anti-Nephi-Lehies, descendantsCovenant, mothers had covenanted not to fight]
-
A.
covenantalLineage
chosen
Indicates a relationship in which one entity belongs to, or is derived from, a line of individuals bound together by a formal or sacred covenant.
-
B.
CenterOfCovenant
Indicates that an entity serves as the primary focal point or core location around which a covenant or formal agreement is established or organized.
-
C.
signOfCovenant
Indicates that something serves as a visible or symbolic marker confirming the existence and terms of a covenant between parties.
-
D.
ofDescent
Indicates a genealogical or ancestral relationship, specifying that one entity descends from or originates from another.
-
E.
covenantAdopted
Indicates that a covenant has been formally accepted and put into effect by the relevant party or parties.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:48 p.m.