Triple
T5488315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saka |
E123639
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Sakan |
E123639
|
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: Sakan | Statement: [Saka, alsoKnownAs, Sakan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sakan Context triple: [Saka, alsoKnownAs, Sakan]
-
A.
Sakaar
Sakaar is a chaotic, trash-covered planet ruled by the Grandmaster in the Marvel Cinematic Universe, known for its gladiatorial contests and bizarre cosmic detritus.
-
B.
Saka
chosen
Saka is an ancient Eastern Iranian language once spoken by the Saka people in the Tarim Basin region of Central Asia.
-
C.
Sadozai
Sadozai is a Pashtun royal dynasty and clan historically associated with the founding rulers of the Durrani Empire in Afghanistan.
-
D.
Shinaki
Shinaki is an alternative name for the Shina people, an ethnic group primarily inhabiting the mountainous regions of northern Pakistan and parts of India.
-
E.
Shiban
Shiban was a Mongol prince of the Golden Horde, a son of Jochi and grandson of Genghis Khan who founded the Shibanid line.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9264d014819097c83bb5c2bb8c39 |
completed | March 20, 2026, 6:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf48aa12708190add69c5fd51d161d |
completed | March 22, 2026, 1:40 a.m. |
Created at: March 20, 2026, 2:10 p.m.