Triple
T6517981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hijri calendar |
E148311
|
entity |
| Predicate | startYearGregorianApprox |
P13193
|
FINISHED |
| Object | 622 CE |
—
|
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: 622 CE | Statement: [Hijri calendar, startYearGregorianApprox, 622 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startYearGregorianApprox Context triple: [Hijri calendar, startYearGregorianApprox, 622 CE]
-
A.
approximateStartCenturyBC
Indicates that an entity’s starting time or occurrence is approximately located within a specified century before the Common Era (BC).
-
B.
yearInGregorianCalendar
Indicates that a specified year is measured according to the Gregorian calendar system.
-
C.
approximateStartYear
chosen
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
-
D.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
E.
approximateStartCentury
Indicates the century in which something is estimated or roughly believed to have begun.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac108abc819082d1368af6611a92 |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.