Triple
T25421997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saka era |
E637008
|
entity |
| Predicate | firstMonthInNationalCalendar |
P187553
|
FINISHED |
| Object | Chaitra |
—
|
NE NERFINISHED |
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: Chaitra | Statement: [Saka era, firstMonthInNationalCalendar, Chaitra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMonthInNationalCalendar Context triple: [Saka era, firstMonthInNationalCalendar, Chaitra]
-
A.
commandedAsFirstMonthIn
Indicates that an entity is designated or ordered to serve as the first month within a specified temporal system or context.
-
B.
majorFestivalMonthGregorian
Indicates the Gregorian calendar month in which a major festival associated with an entity takes place.
-
C.
firstInternationalDate
Indicates that one entity is the earliest (chronologically first) international date associated with another entity.
-
D.
startDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which something was first put into use or began to be used.
-
E.
endDateFirstUseGregorian
Indicates the calendar date, expressed in the Gregorian system, on which the first use of something ended or ceased.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb6fdab95c81909acff3c6a2359787 |
completed | May 6, 2026, 4:44 p.m. |
Created at: April 21, 2026, 1:56 p.m.