Triple
T30974819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nephi |
E789201
|
entity |
| Predicate | receivedCommandmentFrom |
P99420
|
FINISHED |
| Object | God |
—
|
NE NERFINISHED |
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: God | Statement: [Nephi, receivedCommandmentFrom, God]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivedCommandmentFrom Context triple: [Nephi, receivedCommandmentFrom, God]
-
A.
receivedInstructionAbout
Indicates that one entity has been given or obtained guidance, directions, or information concerning another entity or topic.
-
B.
receivedImperialOrderFrom
Indicates that one entity has been formally given an official command or directive by an imperial authority or ruler.
-
C.
receivedRuleFrom
chosen
Indicates that one entity has obtained or been given a rule from another entity.
-
D.
containsCommandment
Indicates that one entity includes or encompasses a specific commandment as part of its content or structure.
-
E.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
- 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_69f224c4831c8190be53924ec25a150a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 29, 2026, 8:55 p.m.