Triple
T31503461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zarahemla |
E803749
|
entity |
| Predicate | unitedPeoples |
P35330
|
FINISHED |
| Object | Nephites and people of Zarahemla |
—
|
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: Nephites and people of Zarahemla | Statement: [Zarahemla, unitedPeoples, Nephites and people of Zarahemla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unitedPeoples Context triple: [Zarahemla, unitedPeoples, Nephites and people of Zarahemla]
-
A.
unites
chosen
Indicates that one entity brings together multiple entities into a single, cohesive whole or shared state.
-
B.
oftenUnitedWith
Indicates that two entities are frequently joined, combined, or associated together as a common or recurring unit.
-
C.
unitedWithTitle
Indicates that an entity has been joined or merged with another entity under a shared or combined title.
-
D.
reunitedAs
Indicates that entities who were previously separated have come back together or been brought back into association.
-
E.
unitedTitle
Indicates that multiple titles have been combined or merged into a single, unified title.
- 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.