Triple
T14799283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Optila |
E347863
|
entity |
| Predicate | ethnicity |
P194
|
FINISHED |
| Object | Hun |
E1103873
|
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: Hun | Statement: [Optila, ethnicity, Hun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hun Context triple: [Optila, ethnicity, Hun]
-
A.
Hun
chosen
The Huns were a nomadic confederation of Central Asian horsemen who became infamous in late antiquity for their fierce military campaigns and invasions of Europe.
-
B.
Huny
Huny is an alternative transliteration of Huni, an ancient Egyptian pharaoh of the Third Dynasty.
-
C.
Huni
Huni was an ancient Egyptian pharaoh of the late Third Dynasty, regarded as one of the last rulers of the Old Kingdom’s early period.
-
D.
Hūr
Hūr are the beautiful, pure companions described in Islamic tradition as residing in Paradise and promised as a reward to the righteous.
-
E.
Khün
Khün refers to the Tai Khün people, a Tai ethnic group primarily inhabiting the Kengtung region of eastern Myanmar, known for their distinct language and cultural traditions.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd6131f08190885f1d27b4bfac7a |
completed | April 14, 2026, 11:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe24c2cd848190bb0d8e4b5f7a489c |
completed | May 8, 2026, 6 p.m. |
Created at: April 10, 2026, 1:31 a.m.