Triple
T15454499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ventôse |
E371733
|
entity |
| Predicate | startDateRule |
P118862
|
FINISHED |
| Object | begins around 19 or 20 February |
—
|
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: begins around 19 or 20 February | Statement: [Ventôse, startDateRule, begins around 19 or 20 February]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDateRule Context triple: [Ventôse, startDateRule, begins around 19 or 20 February]
-
A.
startDateConstraint
Indicates a restriction or condition placed on when something is allowed to start, typically specifying valid or required start dates.
-
B.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
C.
startDateNewStyle
Indicates the date on which something begins, expressed according to the New Style (Gregorian) calendar rather than the Old Style (Julian) calendar.
-
D.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
E.
startsOnDay
Indicates that an event or process begins on a specified calendar day.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:31 a.m.