Triple
T25421985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saka era |
E637008
|
entity |
| Predicate | hasYearZero |
P6439
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Saka era, hasYearZero, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYearZero Context triple: [Saka era, hasYearZero, no]
-
A.
hasApproxGregorianStart
Indicates that an entity has an associated start date expressed as an approximate value in the Gregorian calendar.
-
B.
doesNotUseLeapMonths
Indicates that the referenced calendar or timekeeping system does not incorporate leap months to adjust for discrepancies between its cycle and the astronomical year.
-
C.
yearZero
chosen
Indicates that the referenced year is designated as the starting point (year 0) of a particular calendar, timeline, or counting system.
-
D.
hasNoFixedGregorianDates
Indicates that the associated event or occurrence does not recur on the same fixed dates in the Gregorian calendar each time it happens.
-
E.
calendarYearOffsetFromGregorian
Indicates the number of whole calendar years by which a given calendar system is offset relative to the Gregorian calendar.
- 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_69e75db4135881909acc287ebcb7a505 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6bd517c819086c0e8e9c2dce972 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:56 p.m.