Triple
T6718479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muharram |
E153332
|
entity |
| Predicate | occursEverySolarYearEarlierBy |
P72863
|
FINISHED |
| Object | about 10 to 11 days |
—
|
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: about 10 to 11 days | Statement: [Muharram, occursEverySolarYearEarlierBy, about 10 to 11 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursEverySolarYearEarlierBy Context triple: [Muharram, occursEverySolarYearEarlierBy, about 10 to 11 days]
-
A.
chronologyPreviousYear
Indicates that one time-related entity occurs exactly one calendar year before another in a chronological sequence.
-
B.
occursAfterLeapMonthInLeapYears
Indicates that the referenced event or time period takes place after the leap month specifically in years that are designated as leap years.
-
C.
occursInYearsOfCycle
Indicates that an event or phenomenon takes place during specific years within a recurring multi-year cycle.
-
D.
occurs46DaysBefore
Indicates that one event or action takes place exactly 46 days earlier in time than another event or action.
-
E.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d135d27c819088c45839ad0e7bab |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d11fab808190b18160ff3829fcc6 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:07 p.m.