Triple
T30740893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ammaron |
E782686
|
entity |
| Predicate | predecessorAsRecordKeeper |
P14604
|
FINISHED |
| Object | Nephi, son of Helaman |
—
|
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: Nephi, son of Helaman | Statement: [Ammaron, predecessorAsRecordKeeper, Nephi, son of Helaman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorAsRecordKeeper Context triple: [Ammaron, predecessorAsRecordKeeper, Nephi, son of Helaman]
-
A.
predecessorInRole
chosen
Indicates that one entity previously held a particular role or position that was later occupied by another entity.
-
B.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
C.
predecessorEstablished
Indicates that one entity was established before another, serving as its predecessor in origin or founding.
-
D.
predecessorInRegency
Indicates that one regent directly preceded another in holding regency authority over the same domain or office.
-
E.
predecessorManagedBy
Indicates that a predecessor entity was managed, overseen, or administered by another entity.
- 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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 29, 2026, 8:38 p.m.