Triple
T14952960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluviôse |
E372843
|
entity |
| Predicate | abolishedEffectiveDate |
P3903
|
FINISHED |
| Object | 1806-01-01 |
—
|
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: 1806-01-01 | Statement: [Pluviôse, abolishedEffectiveDate, 1806-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishedEffectiveDate Context triple: [Pluviôse, abolishedEffectiveDate, 1806-01-01]
-
A.
dateAbolished
chosen
Indicates the date on which something (such as an institution, law, practice, or position) was officially ended or abolished.
-
B.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
C.
abolishedInEffectBy
Indicates that the legal force or practical operation of something is nullified or terminated as a result of another specified action or measure.
-
D.
abolishedDuring
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
-
E.
wasAbolishedBy
Indicates that an institution, practice, law, or entity ceased to exist or operate as a result of an action taken by another entity.
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded690f2e08190ad9dad6dc05a164a |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:39 a.m.