Triple
T19076159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elon the Zebulunite |
E466907
|
entity |
| Predicate | biblicalBookChapterVerses |
P87263
|
FINISHED |
| Object | Judges 12:11–12 |
—
|
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: Judges 12:11–12 | Statement: [Elon the Zebulunite, biblicalBookChapterVerses, Judges 12:11–12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalBookChapterVerses Context triple: [Elon the Zebulunite, biblicalBookChapterVerses, Judges 12:11–12]
-
A.
chapterAndVerse
chosen
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.
-
B.
scripturalChapters
Indicates that one entity is composed of, contains, or is divided into the specified scriptural chapters.
-
C.
positionInBible
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
D.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
E.
neighboringVerseNext
Indicates that one verse directly follows another verse in sequence, making them adjacent neighbors in the text.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e49c7c8190b6ce7b918086b23c |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.