Triple
T36946824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yawm al-Jumu'ah |
E913935
|
entity |
| Predicate | prohibitionDuringPrayer |
P186767
|
FINISHED |
| Object | engaging in trade |
—
|
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: engaging in trade | Statement: [Yawm al-Jumu'ah, prohibitionDuringPrayer, engaging in trade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prohibitionDuringPrayer Context triple: [Yawm al-Jumu'ah, prohibitionDuringPrayer, engaging in trade]
-
A.
precedesPrayer
Indicates that one event, action, or state occurs before a prayer in time.
-
B.
ihramProhibitions
Indicates the set of actions or behaviors that are religiously forbidden to a person while they are in the state of ihram.
-
C.
canBePrayed
Indicates that an entity is a suitable or valid target for prayer or religious supplication.
-
D.
prayedDuring
Indicates that one entity performed prayer at some time within the duration of another specified event or time interval.
-
E.
doesNotRequireMinyanFor
Indicates that the associated action, ritual, or obligation can be performed without the presence of a quorum (minyan) of participants.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.