Triple
T6847086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shawwal |
E157923
|
entity |
| Predicate | timezoneBasis |
P73487
|
FINISHED |
| Object | Islamic lunar sightings |
—
|
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: Islamic lunar sightings | Statement: [Shawwal, timezoneBasis, Islamic lunar sightings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timezoneBasis Context triple: [Shawwal, timezoneBasis, Islamic lunar sightings]
-
A.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
B.
timeZoneType
Indicates the classification or category of a time zone associated with an entity (e.g., standard, daylight, or specific time zone format/type).
-
C.
relatedTimeZone
Indicates that two entities are associated with or operate within the same or corresponding time zone(s).
-
D.
timeZoneOriginDST
Indicates that the relationship specifies the original time zone of an entity, including whether daylight saving time (DST) is in effect.
-
E.
timeZonePractice
Indicates that an entity conducts activities or operations according to a particular time zone or set of time zone rules.
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d7cd0e64819097c9c211df8bce54 |
completed | March 27, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d623aba88190a93ec9c83508c960 |
completed | March 27, 2026, 7:10 p.m. |
Created at: March 27, 2026, 2:20 p.m.