Triple
T12027784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | יִשְׁבָּק |
E286321
|
entity |
| Predicate | hasLatinTransliteration |
P76738
|
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: [יִשְׁבָּק, hasLatinTransliteration, Yishbaq]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yishbaq Context triple: [יִשְׁבָּק, hasLatinTransliteration, 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.
Bakhah
Bakhah is a village in Syria known as one of the few remaining communities where Western Neo-Aramaic is still actively spoken.
-
C.
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.
-
D.
Ghebala
Ghebala is a town and commune located within Jijel Province in northeastern Algeria.
-
E.
Bisha
Bisha is a major inland city in southwestern Saudi Arabia known for its agricultural production and strategic location within the Asir region.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903f13ae8819097a5740f7c51df82 |
completed | April 10, 2026, 2:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f646423c819088575a7032e6a9a3 |
completed | May 2, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:47 p.m.