Triple
T15454408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vendémiaire |
E371730
|
entity |
| Predicate | endDateApproximationInGregorianCalendar |
P35259
|
FINISHED |
| Object | around 21 or 22 October |
—
|
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: around 21 or 22 October | Statement: [Vendémiaire, endDateApproximationInGregorianCalendar, around 21 or 22 October]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endDateApproximationInGregorianCalendar Context triple: [Vendémiaire, endDateApproximationInGregorianCalendar, around 21 or 22 October]
-
A.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
B.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
typicalEndDateRange
Indicates the usual or expected range of end dates associated with an event, activity, or time-bounded entity.
-
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_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.