Triple
T4761055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibzan |
E105697
|
entity |
| Predicate | sourceTextVerses |
P28117
|
FINISHED |
| Object | Judges 12:8–10 |
—
|
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:8–10 | Statement: [Ibzan, sourceTextVerses, Judges 12:8–10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceTextVerses Context triple: [Ibzan, sourceTextVerses, Judges 12:8–10]
-
A.
containsVerse
chosen
Indicates that one entity (typically a text or collection) includes a specific verse as part of its content.
-
B.
featuresAdditionalVersesBy
Indicates that a work includes extra or bonus verses contributed by another creator beyond the primary one.
-
C.
scripturalCorpus
Indicates that one entity is a body of scriptural or sacred texts associated with, or serving as the canonical writings for, another entity.
-
D.
keyVerse
Indicates that one verse is designated as the central or most thematically important verse in relation to a text, passage, or concept.
-
E.
recognizesScripturesFrom
Indicates that one entity acknowledges or accepts certain scriptures as authoritative or valid based on another entity as their source or origin.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650eefe08190b99f9f01b121dbfd |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.