Triple
T3611205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamutal |
E76490
|
entity |
| Predicate | biblicalBookChapterVerse |
P21149
|
FINISHED |
| Object | 2 Kings 23:31 |
—
|
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: 2 Kings 23:31 | Statement: [Hamutal, biblicalBookChapterVerse, 2 Kings 23:31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biblicalBookChapterVerse Context triple: [Hamutal, biblicalBookChapterVerse, 2 Kings 23:31]
-
A.
positionInBible
chosen
Indicates the specific location or order of a passage, verse, or book within the structured sequence of the Bible.
-
B.
containsVerse
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
C.
scripturalSection
Indicates a relationship where one text or passage is a specific section or subdivision within a larger scriptural work.
-
D.
verseNumber
Indicates the specific numbered position of a verse within an ordered sequence, such as in a chapter, song, or poem.
-
E.
numberInBiblicalText
Indicates that a specific number appears within, or is referenced by, a given passage or unit of biblical 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_69ad85da0ba481908b3b48c69efe2b98 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc22cac3c8190bc5f7c45d31668c1 |
completed | March 8, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69adb83d8b1c8190b3bddbc5dc995a87 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.