Triple
T913561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Execution of Louis XVI |
E19717
|
entity |
| Predicate | FrenchRevolutionaryCalendarDate |
P17028
|
FINISHED |
| Object | 2 Pluviôse Year I |
—
|
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: 2 Pluviôse Year I | Statement: [Execution of Louis XVI, FrenchRevolutionaryCalendarDate, 2 Pluviôse Year I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FrenchRevolutionaryCalendarDate Context triple: [Execution of Louis XVI, FrenchRevolutionaryCalendarDate, 2 Pluviôse Year I]
-
A.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
B.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
C.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
D.
dateOfExecutionOfLouisXVI
chosen
Indicates the specific calendar date on which the execution of Louis XVI took place.
-
E.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b6755c488190b7f7848110e3ea2c |
completed | March 1, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69a4b292d3408190947cbc2f794cf8c5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:39 p.m.