Triple
T25961075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chennai Music Season |
E645538
|
entity |
| Predicate | calendarMonthCorrespondence |
P1167
|
FINISHED |
| Object | mid-December to mid-January |
—
|
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: mid-December to mid-January | Statement: [Chennai Music Season, calendarMonthCorrespondence, mid-December to mid-January]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarMonthCorrespondence Context triple: [Chennai Music Season, calendarMonthCorrespondence, mid-December to mid-January]
-
A.
calendarVariesBy
Indicates that the characteristics or values of a calendar (such as dates, events, or structure) change depending on another specified factor or context.
-
B.
calendarDependence
Indicates that one event, action, or condition is determined, constrained, or triggered by a specific date, time, or calendar schedule.
-
C.
monthObserved
chosen
Indicates the month during which an event, observation, or measurement took place.
-
D.
calendarType
Indicates the type or system of calendar associated with an entity (e.g., Gregorian, lunar, fiscal).
-
E.
monthSystem
Indicates the calendar or timekeeping system within which a given month is defined or measured.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604c60fe0819092ad09d1c5b0c100 |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:47 a.m.