Triple

T21531195
Position Surface form Disambiguated ID Type / Status
Subject Mercedonius E531233 entity
Predicate instanceOf P0 FINISHED
Object month in the Roman calendar C44923 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: month in the Roman calendar
Context triple: [Mercedonius, instanceOf, month in the Roman calendar]
  • A. date in the Roman calendar
    A date in the Roman calendar represents a specific day identified relative to fixed monthly reference points (Kalends, Nones, Ides) within a particular month and year of the Roman timekeeping system.
  • B. Mesopotamian month
    A Mesopotamian month is a lunar-based time unit in ancient Mesopotamian calendars, typically beginning with the first visible crescent of the moon and used to structure religious festivals, agricultural activities, and administrative records.
  • C. Akkadian month name
    An Akkadian month name is a designation used in the ancient Mesopotamian calendar system to identify and organize specific lunar months for administrative, religious, and agricultural purposes.
  • D. Athenian month
    An Athenian month is a unit of time in the ancient Athenian lunisolar calendar, typically beginning with the first sighting of the new moon and used to organize religious festivals, civic events, and legal deadlines.
  • E. Hindu lunar fortnight
    A Hindu lunar fortnight is a half-month period in the Hindu calendar, consisting of approximately 15 lunar days (tithis) between either a new moon and full moon (shukla paksha) or a full moon and new moon (krishna paksha).
  • F. None of above. chosen

Provenance (1 batch)

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_69e0c45e5b8881908ac18fc2f493b114 completed April 16, 2026, 11:13 a.m.
Created at: April 16, 2026, 6:27 p.m.