Triple
T14096539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shehri language |
E339266
|
entity |
| Predicate | alternativeName |
P39
|
FINISHED |
| Object | Jibbali |
E290155
|
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: Jibbali | Statement: [Shehri language, alternativeName, Jibbali]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jibbali Context triple: [Shehri language, alternativeName, Jibbali]
-
A.
Jabriya
Jabriya is a residential suburb in Kuwait known for its mix of apartment buildings, schools, and local shops within the Hawalli Governorate.
-
B.
Jableh
Jableh is a coastal city in northwestern Syria on the Mediterranean Sea, known for its ancient history and archaeological sites, including a well-preserved Roman theater.
-
C.
Dhiban
Dhiban is an archaeological site and modern town in Jordan, historically significant as the ancient Moabite city of Dibon.
-
D.
Hadibu
chosen
Hadibu is the main town and administrative center of the Yemeni island of Socotra in the Arabian Sea.
-
E.
Ghebala
Ghebala is a town and commune located within Jijel Province in northeastern Algeria.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb926288190a7f0f50d1d585d76 |
completed | April 14, 2026, 3:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd0adfc28819097a1bfd56739c286 |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:22 p.m.