Triple
T27617826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilderness of Beersheba |
E700485
|
entity |
| Predicate | hasNameInScripture |
P184841
|
FINISHED |
| Object | wilderness of Beersheba |
—
|
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: wilderness of Beersheba | Statement: [Wilderness of Beersheba, hasNameInScripture, wilderness of Beersheba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInScripture Context triple: [Wilderness of Beersheba, hasNameInScripture, wilderness of Beersheba]
-
A.
hasScripture
Indicates that one entity possesses, is associated with, or is defined by a particular scripture or set of scriptural texts.
-
B.
scripturalBookNamedAfter
Indicates that a scriptural book bears the name of a particular person, place, or entity.
-
C.
recognizesScripturesFrom
Indicates that one entity acknowledges or accepts certain scriptures as authoritative or valid based on another entity as their source or origin.
-
D.
hasViewOnScripture
Indicates that an entity holds a particular interpretive stance or doctrinal position regarding scripture.
-
E.
inScripture
Indicates that something is mentioned, described, or referenced within a scriptural or sacred text.
- F. None of above. chosen
Provenance (4 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 27, 2026, 2:13 p.m.