Triple
T18746912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .ye |
E458428
|
entity |
| Predicate | registry |
P86
|
FINISHED |
| Object | TeleYemen |
E1341271
|
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: TeleYemen | Statement: [.ye, registry, TeleYemen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TeleYemen Context triple: [.ye, registry, TeleYemen]
-
A.
TeleYemen
chosen
TeleYemen is Yemen’s primary telecommunications company, providing international and domestic voice and data services across the country.
-
B.
Tele-Buqa
Tele-Buqa was a late 13th-century khan of the Golden Horde whose brief and turbulent reign was closely tied to the powerful Mongol emir Nogai Khan.
-
C.
Yemeni corner
The Yemeni corner is the southwestern corner of the Kaaba in Mecca, revered in Islamic tradition as a spot where many pilgrims touch or gesture toward it while performing the circumambulation (tawaf).
-
D.
Tel
Tel is the standard three-letter astronomical abbreviation for the southern constellation Telescopium.
-
E.
Telem
Telem is a small Israeli settlement whose name is derived from the biblical term “Telem.”
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e576936cf08190b3c0d2f4e8a616fc |
completed | April 20, 2026, 12:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a05470cbad081908db660e4f265d15e |
completed | May 14, 2026, 3:52 a.m. |
Created at: April 10, 2026, 11:51 a.m.