Triple
T24981732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | En-dor |
E625185
|
entity |
| Predicate | scripturalChapterContext |
P37110
|
FINISHED |
| Object | 1 Samuel 28 |
—
|
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: 1 Samuel 28 | Statement: [En-dor, scripturalChapterContext, 1 Samuel 28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scripturalChapterContext Context triple: [En-dor, scripturalChapterContext, 1 Samuel 28]
-
A.
scriptureContext
Indicates that one entity provides the textual, historical, or thematic scriptural background or setting necessary to interpret or understand another entity.
-
B.
scripturalSection
chosen
Indicates a relationship where one text or passage is a specific section or subdivision within a larger scriptural work.
-
C.
scripturalLanguageContext
Indicates the linguistic or textual context in which a scriptural passage, term, or reference is expressed or interpreted.
-
D.
chapterContext
Indicates that one element provides the surrounding chapter or section in which another element appears or is relevant.
-
E.
scripturalChapters
Indicates that one entity is composed of, contains, or is divided into the specified scriptural chapters.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490636f88190b8e614202f6d7a65 |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:02 a.m.