Triple
T11234226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friday |
E265901
|
entity |
| Predicate | observanceTypeInIslam |
P97975
|
FINISHED |
| Object | weekly holy day |
—
|
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: weekly holy day | Statement: [Friday, observanceTypeInIslam, weekly holy day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observanceTypeInIslam Context triple: [Friday, observanceTypeInIslam, weekly holy day]
-
A.
observance
Indicates the performance or maintenance of a practice, rule, or custom in accordance with prescribed or expected standards.
-
B.
statusInIslamicTradition
Indicates the recognized standing, role, or level of esteem an entity holds within Islamic religious, cultural, or scholarly tradition.
-
C.
observanceVariesBy
Indicates that the way in which something is observed, practiced, or kept differs depending on a specified factor such as group, place, or time.
-
D.
positionInIslam
Indicates the specific religious role, rank, or status an entity holds within the context of Islam.
-
E.
traditionalPracticeInShiaIslam
Indicates that something is recognized or observed as a customary or established religious practice within Shia Islam.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e903b8ec81909f9c89776d35c650 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfdf7a88190aae21572e57ef208 |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.