Triple
T15690961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coup of 18 Fructidor |
E380326
|
entity |
| Predicate | tookPlaceOnRepublicanDate |
P120296
|
FINISHED |
| Object | 18 Fructidor Year V |
—
|
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: 18 Fructidor Year V | Statement: [Coup of 18 Fructidor, tookPlaceOnRepublicanDate, 18 Fructidor Year V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPlaceOnRepublicanDate Context triple: [Coup of 18 Fructidor, tookPlaceOnRepublicanDate, 18 Fructidor Year V]
-
A.
originalInaugurationDate
Indicates the date on which an entity (such as an office, institution, or facility) was first formally inaugurated or put into official operation.
-
B.
becameRepublicOn
Indicates the date or point in time when an entity transitioned to a republican form of government.
-
C.
inaugurationDay
Indicates the specific day on which a formal ceremony is held to induct someone into an official position or office.
-
D.
inaugurationDate
Indicates the date on which an official ceremony formally installs a person into a specific office or position.
-
E.
inauguralEventDate
Indicates the calendar date on which an entity’s first or inaugural event took place.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e0b4d01c9c81909f6b611e8144c838 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 10, 2026, 4:44 a.m.