Triple
T15454601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thermidor |
E371736
|
entity |
| Predicate | notableDateCorrespondsTo |
P925
|
FINISHED |
| Object | 27 July 1794 |
—
|
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: 27 July 1794 | Statement: [Thermidor, notableDateCorrespondsTo, 27 July 1794]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDateCorrespondsTo Context triple: [Thermidor, notableDateCorrespondsTo, 27 July 1794]
-
A.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
notableAnniversaries
Indicates that there are significant commemorative dates or milestones associated with the subject.
-
C.
celebratedDay
Indicates that a particular day is observed, honored, or festively recognized in association with an entity or event.
-
D.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
E.
notableOperationDate
Indicates the date on which a significant or noteworthy operation, event, or activity associated with an entity took place.
- 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.