Triple
T2592257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Israeli civil calendar |
E58147
|
entity |
| Predicate | usesWeekStructure |
P6441
|
FINISHED |
| Object | seven-day week |
—
|
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: seven-day week | Statement: [Israeli civil calendar, usesWeekStructure, seven-day week]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWeekStructure Context triple: [Israeli civil calendar, usesWeekStructure, seven-day week]
-
A.
hasWeekLength
chosen
Indicates the duration of a week associated with an entity, typically expressed as a number of days.
-
B.
hasWeeklyHolyDay
Indicates that an entity observes or is associated with a recurring holy or sacred day that occurs weekly.
-
C.
startDayOfWeek
Indicates the specific day of the week on which a given period, schedule, or recurring event begins.
-
D.
trackingWeekEnd
Indicates the point in time marking when a specified tracking period or tracking week concludes.
-
E.
usesCalendar
Indicates that an entity employs or relies on a calendar system for organizing, tracking, or scheduling dates and events.
- 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_69ab4ac019c8819094add11c46706e32 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd425851c819088db89713c07056f |
completed | March 7, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69abd0d344988190a18dd93b13e002e6 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.