Triple
T8550491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamil calendar |
E202431
|
entity |
| Predicate | hasYearNameSystem |
P71814
|
FINISHED |
| Object | 60-year Jovian cycle |
—
|
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: 60-year Jovian cycle | Statement: [Tamil calendar, hasYearNameSystem, 60-year Jovian cycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYearNameSystem Context triple: [Tamil calendar, hasYearNameSystem, 60-year Jovian cycle]
-
A.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
B.
hasJapaneseEraBirthYear
Indicates that an entity’s birth year is specified according to the Japanese era (gengō) calendar system.
-
C.
hasSolarCalendarName
chosen
Indicates that an entity is associated with a specific name used in a solar calendar system.
-
D.
hasYearType
Indicates a relationship where an entity is associated with a specific classification or category of year (such as calendar, fiscal, academic, or other year type).
-
E.
hasDayNameSystem
Indicates that an entity employs or is associated with a particular system for naming or designating days.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe75589d8819096177ddbd3dafcb6 |
completed | March 31, 2026, 3:25 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:19 p.m.