Triple
T34582960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samson et Dalila |
E887958
|
entity |
| Predicate | biblicalSourceChapter |
P111153
|
FINISHED |
| Object | Book of Judges 13–16 |
—
|
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: Book of Judges 13–16 | Statement: [Samson et Dalila, biblicalSourceChapter, Book of Judges 13–16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalSourceChapter Context triple: [Samson et Dalila, biblicalSourceChapter, Book of Judges 13–16]
-
A.
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.
-
B.
scripturalReference
Indicates that one entity cites, alludes to, or is based on a specific passage or portion of a scriptural text found in another entity.
-
C.
associatedWithBiblicalChapter
chosen
Indicates that something has a specified connection or linkage to a particular chapter in the Bible.
-
D.
scripturalSection
Indicates a relationship where one text or passage is a specific section or subdivision within a larger scriptural work.
-
E.
gospelChapter
Indicates that one entity is a specific chapter within a particular gospel text or book.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720c590008190a21d17b4697c968a |
completed | May 3, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:03 a.m.