Triple
T15606266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mu'tah |
E375167
|
entity |
| Predicate | calendarDateHijri |
P81485
|
FINISHED |
| Object | Jumada al-Awwal 8 AH |
—
|
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: Jumada al-Awwal 8 AH | Statement: [Battle of Mu'tah, calendarDateHijri, Jumada al-Awwal 8 AH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calendarDateHijri Context triple: [Battle of Mu'tah, calendarDateHijri, Jumada al-Awwal 8 AH]
-
A.
dayInIslamicCalendar
Indicates that a specific day corresponds to a particular date in the Islamic (Hijri) calendar.
-
B.
hasCalendarDateHijri
chosen
Indicates that an entity is associated with a specific date expressed in the Hijri (Islamic) calendar.
-
C.
hijriYear
Indicates the Hijri (Islamic lunar calendar) year associated with an event, date, or entity.
-
D.
positionInIslamicCalendar
Indicates the specific placement or ordering of a time point (such as a date or event) within the structure of the Islamic (Hijri) calendar.
-
E.
birthDateHijri
Indicates the date on which an entity was born, expressed according to the Hijri (Islamic) 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7d9328819090e93d55881269a5 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.