Triple
T4887563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saul |
E109473
|
entity |
| Predicate | burialPlace |
P196
|
FINISHED |
| Object | Jabesh-gilead |
E406475
|
NE 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: Jabesh-gilead | Statement: [Saul, burialPlace, Jabesh-gilead]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jabesh-gilead Context triple: [Saul, burialPlace, Jabesh-gilead]
-
A.
Heshbon
Heshbon is an ancient city in the Transjordan region frequently mentioned in the Bible as a significant Moabite and later Israelite center.
-
B.
Gibeah
Gibeah was an ancient Israelite city in the territory of Benjamin, historically notable as the royal seat of King Saul.
-
C.
Kedesh
Kedesh was an ancient city in the territory of the Israelite tribe of Naphtali, known as a Levitical city of refuge in the Hebrew Bible.
-
D.
Gilʿad
chosen
Gilʿad is a biblical region east of the Jordan River, traditionally associated with the ancient Israelite tribes and noted for its rugged terrain and balm-producing plants.
-
E.
Sha'ar Yafo
Sha'ar Yafo is the Hebrew name for Jaffa Gate, one of the main historic entrances to Jerusalem’s Old City.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd440f71348190b99938e59fb7f9a1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e03a7fc8190bcac63f4b19e586e |
completed | March 20, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be68126b288190889b2cf6e400ec0b |
completed | March 21, 2026, 9:42 a.m. |
Created at: March 20, 2026, 1:28 p.m.