Triple
T1267635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julian calendar |
E15636
|
entity |
| Predicate | differenceFromGregorianDaysIn20th21stCenturies |
P11836
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Julian calendar, differenceFromGregorianDaysIn20th21stCenturies, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: differenceFromGregorianDaysIn20th21stCenturies Context triple: [Julian calendar, differenceFromGregorianDaysIn20th21stCenturies, 13]
-
A.
testCenturies
Indicates that an entity has scored one or more centuries (100+ runs) in test cricket matches.
-
B.
dateRelativeToGregorian
chosen
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
C.
standardizedInCentury
Indicates that something was standardized or formally established according to a common norm during a specified century.
-
D.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
E.
isCentennialOf
Indicates that one event, celebration, or marker commemorates the 100th anniversary of another event or entity.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4c0396e048190b4e2d7aab19268b3 |
completed | March 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69a4bede52a081909665d60acbe41d31 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.