Triple

T14099574
Position Surface form Disambiguated ID Type / Status
Subject Sistan E339343 entity
Predicate historicalInhabitants P3032 FINISHED
Object Saka 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: Saka | Statement: [Sistan, historicalInhabitants, Saka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saka
Context triple: [Sistan, historicalInhabitants, Saka]
  • A. Saka chosen
    Saka is an ancient Eastern Iranian language once spoken by the Saka people in the Tarim Basin region of Central Asia.
  • B. 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.
  • C. Shuka
    Shuka is a Japanese animation studio known for producing the later seasons and related works of the urban fantasy anime series Durarara!!.
  • D. Suo-Gân
    Suo-Gân is a traditional Welsh lullaby known for its gentle melody and soothing, lyrical character.
  • E. Saka era
    The Saka era is a historical Indian calendar era that begins in 78 CE and underlies the official national calendar of India and several regional calendars.
  • 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_69de5fba7c10819095b1299b7b4f0310 completed April 14, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd0b108908190b4b408f21ecb877a completed May 7, 2026, 5:49 p.m.
Created at: April 9, 2026, 10:22 p.m.