Triple
T30741190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the brother of Jared |
E782692
|
entity |
| Predicate | scripturalBookChapter |
P37110
|
FINISHED |
| Object | Ether 1 |
—
|
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: Ether 1 | Statement: [the brother of Jared, scripturalBookChapter, Ether 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalBookChapter Context triple: [the brother of Jared, scripturalBookChapter, Ether 1]
-
A.
scripturalChapters
Indicates that one entity is composed of, contains, or is divided into the specified scriptural chapters.
-
B.
chapterAndVerse
Indicates a relationship where a specific chapter is associated with a specific verse (or set of verses) within a structured text, such as a book or document.
-
C.
scripturalSection
chosen
Indicates a relationship where one text or passage is a specific section or subdivision within a larger scriptural work.
-
D.
gospelChapter
Indicates that one entity is a specific chapter within a particular gospel text or book.
-
E.
associatedWithBiblicalChapter
Indicates that something has a specified connection or linkage to a particular chapter in the Bible.
- 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_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 29, 2026, 8:38 p.m.