Triple
T21531282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalends |
E531235
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | day in the Roman calendar |
C24218
|
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: day in the Roman calendar Context triple: [Kalends, instanceOf, day in the Roman calendar]
-
A.
date in the Roman calendar
chosen
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.
day in the Christian liturgical year
A day in the Christian liturgical year is a specific calendar date assigned particular religious significance, observances, and readings within the cycle of Christian worship.
-
C.
solar calendar
A solar calendar is a timekeeping system in which dates are based on the Earth's position in its orbit around the Sun, typically approximating the length of the tropical year.
-
D.
time period in the Jewish calendar
A time period in the Jewish calendar is a defined span of time—such as a day, week, month, festival, or year—structured according to Jewish religious law and tradition for ritual, historical, and communal purposes.
-
E.
event in ancient Rome
An event in ancient Rome is a specific occurrence or happening—such as a political assembly, religious festival, public spectacle, or military action—situated in Roman society and time that holds social, cultural, or historical significance.
- F. None of above.
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.