Triple
T24230139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French monetary reform of 1795 |
E601707
|
entity |
| Predicate | legalBasisCalendar |
P5453
|
FINISHED |
| Object | French Republican Calendar |
—
|
NE NERFINISHED |
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: French Republican Calendar | Statement: [French monetary reform of 1795, legalBasisCalendar, French Republican Calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalBasisCalendar Context triple: [French monetary reform of 1795, legalBasisCalendar, French Republican Calendar]
-
A.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
B.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
-
C.
legalStandingBasis
Indicates the legal grounds or justification on which a party’s standing or authority in a legal matter is based.
-
D.
usesCalendarEvent
Indicates that one entity makes use of, interacts with, or relies on a specific calendar event.
-
E.
calendarType
chosen
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287e3187c8190ab054ad983ed0335 |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:01 a.m.