Triple
T5266155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaanum Pongal |
E118940
|
entity |
| Predicate | typicalGregorianDateRange |
P18044
|
FINISHED |
| Object | 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: January | Statement: [Kaanum Pongal, typicalGregorianDateRange, January]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGregorianDateRange Context triple: [Kaanum Pongal, typicalGregorianDateRange, January]
-
A.
typicalDates
chosen
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
-
B.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
C.
dateSecularized
Indicates the date on which a religious or ecclesiastical entity was formally converted to secular (non-religious) status.
-
D.
dateDetermination
Indicates the process or criteria by which a specific date is identified, calculated, or assigned in relation to an event or condition.
-
E.
dateInAnglicanCommunion
Indicates that a given date is recognized and observed within the liturgical calendar of the Anglican Communion.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77c71268819094f9f5203eed392d |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:51 p.m.