Triple
T30741041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gadianton robbers |
E782689
|
entity |
| Predicate | firstMentionedInChapter |
P42626
|
FINISHED |
| Object | Helaman 2 |
E1894669
|
NE 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: Helaman 2 | Statement: [Gadianton robbers, firstMentionedInChapter, Helaman 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMentionedInChapter Context triple: [Gadianton robbers, firstMentionedInChapter, Helaman 2]
-
A.
firstMentionedInSeries
Indicates the work, episode, or installment in a series where a given entity is introduced or appears for the first time.
-
B.
firstAppearanceChapter
chosen
Indicates the chapter in which an entity (such as a character, item, or concept) is first introduced or appears in a work.
-
C.
foundInChapter
Indicates that something (such as a concept, section, or element) is contained within or occurs in a specific chapter.
-
D.
chapterMentioned
Indicates that a specific chapter is referenced or cited within a given context or source.
-
E.
firstExplicitlyMentionedBy
Indicates that one entity is the earliest known source to explicitly mention or refer to another entity.
- F. None of above.
Provenance (4 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_6a03213d35788190bdf04e19625b4060 |
completed | May 12, 2026, 12:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28991a80b0819093e4d63fabe3e5f1 |
completed | June 9, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_6a031ea131d48190ab0fecb48b8e2205 |
completed | May 12, 2026, 12:35 p.m. |
Created at: April 29, 2026, 8:38 p.m.