Triple
T26309381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ʿĀm al-Ḥuzn |
E661777
|
entity |
| Predicate | approximateGregorianYear |
P61142
|
FINISHED |
| Object | 619 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: 619 CE | Statement: [ʿĀm al-Ḥuzn, approximateGregorianYear, 619 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateGregorianYear Context triple: [ʿĀm al-Ḥuzn, approximateGregorianYear, 619 CE]
-
A.
calendarYearOffsetFromGregorian
Indicates the number of whole calendar years by which a given calendar system is offset relative to the Gregorian calendar.
-
B.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
-
C.
yearInGregorianCalendar
chosen
Indicates that a specified year is measured according to the Gregorian calendar system.
-
D.
approximateYearInIslamicCalendar
Indicates that the associated year value is an estimated or non-exact year expressed in the Islamic (Hijri) calendar.
-
E.
leapYearGregorianDate
Indicates that a given date falls in a year that is a leap year according to the rules of 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 26, 2026, 10:21 p.m.