Triple
T31311365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epip |
E798470
|
entity |
| Predicate | typicalGregorianStartApprox |
—
|
GENERATED |
| Object | July 8 |
—
|
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: typicalGregorianStartApprox Context triple: [Epip, typicalGregorianStartApprox, July 8]
-
A.
startDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which something was first put into use or began to be used.
-
B.
endDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which the first use of something ended or ceased.
-
C.
hasApproxGregorianStart
chosen
Indicates that an entity has an associated start date expressed as an approximate value in the Gregorian calendar.
-
D.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:15 p.m.