Triple
T8550488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil calendar |
E202431
|
entity |
| Predicate | hasEra |
P561
|
FINISHED |
| Object | Saka era |
E637008
|
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 era | Statement: [Tamil calendar, hasEra, Saka era]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saka era Context triple: [Tamil calendar, hasEra, Saka era]
-
A.
Saka era
chosen
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.
-
B.
Saka
Saka is an ancient Eastern Iranian language once spoken by the Saka people in the Tarim Basin region of Central Asia.
-
C.
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.
-
D.
Sanakhte
Sanakhte was an early ancient Egyptian pharaoh traditionally associated with the 3rd Dynasty and sometimes considered a predecessor or relative of Djoser.
-
E.
Sakakah
Sakakah is a city in northwestern Saudi Arabia that serves as the administrative and economic center of the Al Jawf Region.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe75589d8819096177ddbd3dafcb6 |
completed | March 31, 2026, 3:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce6dc1bb5481909ddd3af564c24c0c |
completed | April 2, 2026, 1:23 p.m. |
Created at: March 30, 2026, 6:19 p.m.