Triple
T15605404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Floréal |
E375146
|
entity |
| Predicate | typicalGregorianCorrespondence |
P11836
|
FINISHED |
| Object | late April to late May |
—
|
LITERAL 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: late April to late May | Statement: [Floréal, typicalGregorianCorrespondence, late April to late May]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGregorianCorrespondence Context triple: [Floréal, typicalGregorianCorrespondence, late April to late May]
-
A.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
B.
calendarYearOffsetFromGregorian
Indicates the number of whole calendar years by which a given calendar system is offset relative to the Gregorian calendar.
-
C.
dateRelativeToGregorian
chosen
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
D.
accuracyComparedToJulian
Indicates how the accuracy of something compares to that of the Julian calendar as a reference standard.
-
E.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
- F. None of above.
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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7d9328819090e93d55881269a5 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.