Triple
T29211626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vaikasi |
E740558
|
entity |
| Predicate | positionInTamilYear |
P74840
|
FINISHED |
| Object | second month in the Tamil calendar |
—
|
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: second month in the Tamil calendar | Statement: [Vaikasi, positionInTamilYear, second month in the Tamil calendar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTamilYear Context triple: [Vaikasi, positionInTamilYear, second month in the Tamil calendar]
-
A.
monthInTamilCalendar
chosen
Indicates that one entity is a specific month as defined in the Tamil calendar system.
-
B.
positionInCivilYear
Indicates the specific point or ordering of something within the sequence of time units that make up a civil (calendar) year.
-
C.
positionInSaptarishi
Indicates the specific place or ordering that an entity occupies within the Saptarishi group.
-
D.
positionInHebrewCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Hebrew calendar.
-
E.
tithiNumber
Indicates the specific numerical position or count of a tithi (lunar day) within a lunar month or cycle.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: April 28, 2026, 12:11 p.m.