Triple
T14096515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hobyot language |
E339265
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Hobyōt |
E347906
|
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: Hobyōt | Statement: [Hobyot language, hasAlternativeName, Hobyōt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hobyōt Context triple: [Hobyot language, hasAlternativeName, Hobyōt]
-
A.
Hobokan
Hobokan is an alternative name or spelling for the place or entity known as Hobuck.
-
B.
Hobyot
chosen
Hobyot is a rare and severely endangered South Semitic language spoken by small communities in eastern Yemen and western Oman.
-
C.
Hobyo
Hobyo is a historic coastal town and port on the Indian Ocean in central Somalia, known for its strategic location and role in regional trade.
-
D.
Shobijin
Shobijin are the tiny twin priestesses who serve as Mothra’s mystical spokespeople and guardians in the Godzilla and broader kaiju film universe.
-
E.
Hōan
Hōan was a Japanese era name (nengō) of the early 12th century, used during the reign of Emperor Toba.
- 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_69fd54fc136881908f0ff5cafa604811 |
completed | May 8, 2026, 3:14 a.m. |
Created at: April 9, 2026, 10:22 p.m.