Triple
T21531258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalends |
E531234
|
entity |
| Predicate | positionInMonth |
P144731
|
FINISHED |
| Object | first day of the month |
—
|
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: first day of the month | Statement: [Kalends, positionInMonth, first day of the month]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInMonth Context triple: [Kalends, positionInMonth, first day of the month]
-
A.
positionInWheelOfYear
Indicates the specific place or phase an event, festival, or time period occupies within the cyclical sequence of the Wheel of the Year.
-
B.
monthObserved
Indicates the month during which an event, observation, or measurement took place.
-
C.
positionInCivilYear
Indicates the specific point or ordering of something within the sequence of time units that make up a civil (calendar) year.
-
D.
positionInGregorianCalendar
Indicates the specific placement or ordering of a time-related entity within the structure of the Gregorian calendar.
-
E.
monthNumber
Indicates the numerical position of a month within a calendar year (e.g., January = 1, February = 2, etc.).
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d08ebf881909574e098404f93fa |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:27 p.m.