Triple
T24283106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night of Measure |
E605595
|
entity |
| Predicate | believedDateRange |
P82593
|
FINISHED |
| Object | last ten nights of Ramadan |
—
|
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: last ten nights of Ramadan | Statement: [Night of Measure, believedDateRange, last ten nights of Ramadan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: believedDateRange Context triple: [Night of Measure, believedDateRange, last ten nights of Ramadan]
-
A.
approximateYearRange
Indicates that the associated time span is not exact but falls within an estimated or approximate range of years.
-
B.
chronologicalRange
chosen
Indicates the temporal span or period over which something occurs, is valid, or is relevant.
-
C.
approximateInceptionPeriod
Indicates an estimated or loosely defined time period during which something began or came into existence.
-
D.
seasonSpan
Indicates the time period or range of dates over which a particular season extends or is in effect.
-
E.
approximateStartYear
Indicates that the associated year value represents an estimated or imprecise starting year for an event, state, or relationship rather than an exact one.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f53a8448190b66f6a97544bacc1 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.