Triple
T25232728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Malayalam calendar |
E632257
|
entity |
| Predicate | startsYearOn |
P162572
|
FINISHED |
| Object | Chingam 1 |
—
|
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: Chingam 1 | Statement: [Malayalam calendar, startsYearOn, Chingam 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startsYearOn Context triple: [Malayalam calendar, startsYearOn, Chingam 1]
-
A.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
B.
typicalStartYear
Indicates the year in which something (such as an event, activity, or process) usually or customarily begins.
-
C.
laterTypeStartYear
Indicates that the starting year of one type or classification occurs later in time than the starting year of another type or classification.
-
D.
assemblyStartYear
Indicates the calendar year in which an assembly process or assembly-related activity begins.
-
E.
contractStartYear
Indicates the calendar year in which a contract between parties officially begins.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f627ad6d4c81909796d39d78e414f9 |
completed | May 2, 2026, 4:34 p.m. |
Created at: April 21, 2026, 1:06 p.m.