Triple
T14952954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pluviôse |
E372843
|
entity |
| Predicate | dayStructure |
P63429
|
FINISHED |
| Object | 10-day weeks |
—
|
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: 10-day weeks | Statement: [Pluviôse, dayStructure, 10-day weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dayStructure Context triple: [Pluviôse, dayStructure, 10-day weeks]
-
A.
dayPattern
chosen
Indicates the recurring schedule or configuration of days on which an event, action, or condition occurs.
-
B.
dayType
Indicates the classification or category of a given day based on its characteristics or role (e.g., weekday, weekend, holiday).
-
C.
dayTypeVariation
Indicates a relationship where the type or classification of a day differs from a standard or reference day type (e.g., special, holiday, or exceptional schedule).
-
D.
weekdayServicePattern
Indicates a service pattern or schedule that specifically applies on weekdays rather than weekends or holidays.
-
E.
dayBeginsAt
Indicates the specific time at which a given day starts.
- 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.