Triple
T2648650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishbak |
E53843
|
entity |
| Predicate | nameTransliteration |
P5923
|
FINISHED |
| Object | Yishbaq |
E53843
|
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: Yishbaq | Statement: [Ishbak, nameTransliteration, Yishbaq]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yishbaq Context triple: [Ishbak, nameTransliteration, Yishbaq]
-
A.
Ishbak
chosen
Ishbak is a lesser-known son of the biblical patriarch Abraham, mentioned among the children he had later in life.
-
B.
Bisha
Bisha is a major inland city in southwestern Saudi Arabia known for its agricultural production and strategic location within the Asir region.
-
C.
Ishkur
Ishkur is a Mesopotamian storm and rain god associated with thunder, fertility, and seasonal weather.
-
D.
Yishai
Yishai is the Hebrew form of the biblical name Jesse, known as the father of King David in the Hebrew Bible.
-
E.
Hillah
Hillah is a city in central Iraq on the Euphrates River, known as the modern settlement adjacent to the ruins of ancient Babylon.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd91b4b3c81908571e85a1621dfc5 |
completed | March 7, 2026, 7:51 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af98c944548190a8dbe9b81045e97b |
completed | March 10, 2026, 4:06 a.m. |
Created at: March 6, 2026, 9:53 p.m.