Triple
T32348680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Africa/Casablanca |
E826533
|
entity |
| Predicate | hasRamadanTimeAdjustmentsHistorically |
P188804
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Africa/Casablanca, hasRamadanTimeAdjustmentsHistorically, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRamadanTimeAdjustmentsHistorically Context triple: [Africa/Casablanca, hasRamadanTimeAdjustmentsHistorically, true]
-
A.
hasHistoricalPermanentDSTExperiment
Indicates that an entity has undergone a historically significant, long-term or permanent daylight saving time experiment or trial.
-
B.
historicalDSTUsage
Indicates that there was a period in the past when the entity or location observed daylight saving time, even if it may not do so currently.
-
C.
timeWithMuhammad
Indicates that one entity spends or has spent time together with Muhammad.
-
D.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
E.
changeOfQiblaOccurredDuring
Indicates that a change in the direction of Qibla took place during the time span or event associated with the related entity.
- 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_69f34914dfc48190a390cd0720d9e86f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbad1b3ba08190ad69e21461333f2e |
completed | May 6, 2026, 9:05 p.m. |
Created at: May 1, 2026, 12:49 a.m.