Triple
T6568794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhu al-Qadah |
E155379
|
entity |
| Predicate | sacredMonthNumber |
P71919
|
FINISHED |
| Object | first of the three consecutive sacred months |
—
|
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: first of the three consecutive sacred months | Statement: [Dhu al-Qadah, sacredMonthNumber, first of the three consecutive sacred months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredMonthNumber Context triple: [Dhu al-Qadah, sacredMonthNumber, first of the three consecutive sacred months]
-
A.
monthInHinduCalendar
Indicates that a specified time or event falls within a particular month as defined by the Hindu calendar system.
-
B.
monthInIslamicCalendar
Indicates that one entity is a specific month within the Islamic (Hijri) calendar system.
-
C.
monthObserved
Indicates the month during which an event, observation, or measurement took place.
-
D.
monthOfBengaliCalendar
Indicates that one entity specifies the month associated with a date or event according to the Bengali calendar.
-
E.
monthNumber
Indicates the numerical position of a month within a calendar year (e.g., January = 1, February = 2, etc.).
- F. None of above. chosen
Provenance (4 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_69c688151254819080387f87deab8fa7 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 1:53 p.m.