Triple
T31503527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Mosiah I |
E803750
|
entity |
| Predicate | unifiedPeople |
P164584
|
FINISHED |
| Object | Nephites and Mulekites |
—
|
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: Nephites and Mulekites | Statement: [King Mosiah I, unifiedPeople, Nephites and Mulekites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unifiedPeople Context triple: [King Mosiah I, unifiedPeople, Nephites and Mulekites]
-
A.
personalUnionResult
Indicates that a personal union between entities has occurred and specifies the resulting combined political or dynastic arrangement.
-
B.
territoryUnifiedWith
Indicates that two or more territories have been politically or administratively merged into a single unified territorial entity.
-
C.
unifiedFrom
chosen
Indicates that multiple separate entities or components have been combined into a single unified entity or representation.
-
D.
primaryAllianceUsers
Indicates that the subject entity has users who are designated as primary members or participants within an alliance or allied group.
-
E.
alliedUsers
Indicates that two users are in an alliance or cooperative relationship with each other.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a214a24481908d30547f6d36aabe |
completed | May 3, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:45 p.m.