Triple
T1940353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iranian peoples |
E41537
|
entity |
| Predicate | hasPart |
P35
|
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: [Iranian peoples, hasPart, Saka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saka Context triple: [Iranian peoples, hasPart, 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.
Sokar
Sokar is an ancient Egyptian funerary god associated with the Memphite necropolis, the afterlife, and aspects of death and rebirth.
-
D.
Hira
Hira is the ISO 15924 script code representing the Japanese hiragana writing system.
-
E.
Kanuma
Kanuma is a regional harvest festival celebrated mainly in Andhra Pradesh and Telangana as part of the multi-day Makar Sankranti festivities, focusing on cattle worship and agricultural prosperity.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2ca385c8190ad0e4bafbb9b5e5c |
completed | March 7, 2026, 5:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adf3f81e0c819090e3f2154215ff18 |
completed | March 8, 2026, 10:11 p.m. |
Created at: March 4, 2026, 7:36 p.m.