Triple
T15454471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nivôse |
E371732
|
entity |
| Predicate | endsNearGregorianDate |
P11836
|
FINISHED |
| Object | approximately 19 or 20 January |
—
|
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: approximately 19 or 20 January | Statement: [Nivôse, endsNearGregorianDate, approximately 19 or 20 January]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endsNearGregorianDate Context triple: [Nivôse, endsNearGregorianDate, approximately 19 or 20 January]
-
A.
hasApproxGregorianStart
Indicates that an entity has an associated start date expressed as an approximate value in the Gregorian calendar.
-
B.
hasDateInGregorianCalendar
Indicates that an entity is associated with a specific date expressed using the Gregorian calendar system.
-
C.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
D.
followsGregorianCalendar
Indicates that the entity uses or adheres to the Gregorian calendar system for dating and timekeeping.
-
E.
dateRelativeToGregorian
chosen
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f131b1481909ff099c3b844ee07 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded28276f481908c2038bb301e57cf |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:31 a.m.