Triple

T14095717
Position Surface form Disambiguated ID Type / Status
Subject Babylonian calendar E339248 entity
Predicate hasMonthName P92265 FINISHED
Object Tašrītu E389330 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: Tašrītu | Statement: [Babylonian calendar, hasMonthName, Tašrītu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tašrītu
Context triple: [Babylonian calendar, hasMonthName, Tašrītu]
  • A. Tašrītu chosen
    Tašrītu is an alternative transliteration of the Akkadian month name Tashritu, associated with the beginning of the year in the ancient Mesopotamian calendar.
  • B. Tashir
    Tashir is a small town located in Armenia’s northern Lori Province.
  • C. Tarusa
    Tarusa is a small historic town in western Russia known for its scenic location on the Oka River and its associations with Russian artists and writers.
  • D. Tashlultum
    Tashlultum was a queen of the Akkadian Empire, known primarily as the wife of the powerful ruler Naram-Sin.
  • E. Shivta
    Shivta is an ancient Nabatean and Byzantine desert city in Israel, known for its remarkably well-preserved ruins and role along historic trade routes.
  • 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_69de5fb7fb3c819083266dbe7e93aaff completed April 14, 2026, 3:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcd0ac02488190b2114eb63ec604c3 completed May 7, 2026, 5:49 p.m.
Created at: April 9, 2026, 10:22 p.m.