Triple
T10933407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shaybanid dynasty |
E258266
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Shiban |
E347579
|
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: Shiban | Statement: [Shaybanid dynasty, namedAfter, Shiban]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shiban Context triple: [Shaybanid dynasty, namedAfter, Shiban]
-
A.
Shiban
chosen
Shiban was a Mongol prince of the Golden Horde, a son of Jochi and grandson of Genghis Khan who founded the Shibanid line.
-
B.
Seishirō
Seishirō is a Japanese given name commonly used for male individuals.
-
C.
Jeriba Shigan
Jeriba Shigan is a Drac alien pilot who becomes an unlikely ally and close companion to a human soldier in the science fiction story "Enemy Mine."
-
D.
Shimotsuki
Shimotsuki was a Japanese destroyer of the Imperial Japanese Navy that served in World War II before being sunk in late 1944.
-
E.
Shamiya
Shamiya is a residential district in Kuwait City known for its planned layout, community facilities, and central location within the capital.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770ae073881909720febe9f5f296a |
completed | April 9, 2026, 9:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2176328448190bbce6735ec97507a |
completed | April 17, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:23 p.m.