Triple
T15099670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orda |
E360629
|
entity |
| Predicate | sibling |
P363
|
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: [Orda, sibling, Shiban]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shiban Context triple: [Orda, sibling, 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.
Shinshiro
Shinshiro is a city in eastern Aichi Prefecture, Japan, known for its mountainous scenery, historic battle sites, and traditional rural landscapes.
-
C.
Shinjo
Shinjo is a notable figure associated with the Kegon school of Japanese Buddhism, recognized for contributions to its teachings or development.
-
D.
Seishirō
Seishirō is a Japanese given name commonly used for male individuals.
-
E.
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."
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0054f00388190a5123d9f4a869b96 |
completed | April 15, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff01d6ddbc81908b010a54ee728dfe |
completed | May 9, 2026, 9:43 a.m. |
Created at: April 10, 2026, 3:04 a.m.