Triple
T19348237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribe of Gilead |
E483939
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Bashan |
—
|
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: Bashan | Statement: [Tribe of Gilead, borderedBy, Bashan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bashan Context triple: [Tribe of Gilead, borderedBy, Bashan]
-
A.
Bashan
chosen
Bashan is a historically significant region east of the Jordan River, renowned in biblical texts for its fertile lands, strong cities, and mighty cattle.
-
B.
Shemshak
Shemshak is a mountain village and ski resort in the Alborz range of northern Iran, known for its steep slopes and popularity among advanced skiers.
-
C.
Shushan
Shushan is the ancient Persian royal city traditionally identified as the capital where the events of the biblical Book of Esther take place.
-
D.
Bakhah
Bakhah is a village in Syria known as one of the few remaining communities where Western Neo-Aramaic is still actively spoken.
-
E.
Leshem
Leshem is an ancient Canaanite city in the northern Levant, later known as Laish and associated with the biblical tribe of Dan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185c95248190b1e5bb8626489767 |
completed | April 20, 2026, 12:13 p.m. |
Created at: April 10, 2026, 1:34 p.m.