Triple
T30876233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anti-Nephi-Lehies |
E786481
|
entity |
| Predicate | madeCovenantTo |
P11164
|
FINISHED |
| Object | never again shed human blood |
—
|
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: never again shed human blood | Statement: [Anti-Nephi-Lehies, madeCovenantTo, never again shed human blood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeCovenantTo Context triple: [Anti-Nephi-Lehies, madeCovenantTo, never again shed human blood]
-
A.
madeCovenantType
Indicates that a covenant was established, specifying the particular type or category of that covenant relationship.
-
B.
covenantWith
chosen
Indicates a formal, binding agreement or promise established between two or more parties.
-
C.
covenantAdopted
Indicates that a covenant has been formally accepted and put into effect by the relevant party or parties.
-
D.
signOfCovenant
Indicates that something serves as a visible or symbolic marker confirming the existence and terms of a covenant between parties.
-
E.
covenantForm
Indicates that a formal covenant or binding agreement is established or constituted between entities.
- 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_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:48 p.m.