Triple
T35913290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | summer solstice |
E1038678
|
entity |
| Predicate | relatedCalendarSystem |
—
|
GENERATED |
| Object | Gregorian calendar |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedCalendarSystem Context triple: [summer solstice, relatedCalendarSystem, Gregorian calendar]
-
A.
usedInCalendarSystem
chosen
Indicates that something (such as a time unit, era, or convention) is employed as part of a particular calendar system.
-
B.
hasNumberOfWeekSystems
Indicates the relationship that specifies how many distinct week-based systems are associated with or used by a given entity.
-
C.
usedCalendarReform
Indicates that one entity adopted or implemented a particular calendar reform associated with another entity.
-
D.
holidayDateSystem
Indicates the system or convention used to determine and represent the date on which a holiday occurs.
-
E.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:07 p.m.