Triple
T31098988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | رمي الجمرات |
E792617
|
entity |
| Predicate | hasTimeConstraint |
P152930
|
FINISHED |
| Object | أوقات محددة للرمي في كل يوم |
—
|
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: أوقات محددة للرمي في كل يوم | Statement: [رمي الجمرات, hasTimeConstraint, أوقات محددة للرمي في كل يوم]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeConstraint Context triple: [رمي الجمرات, hasTimeConstraint, أوقات محددة للرمي في كل يوم]
-
A.
hasTimeOptions
Indicates that an entity is associated with one or more selectable time choices or configurations.
-
B.
hasCutoffTime
Indicates that there is a specific time limit or deadline by which an action, event, or process must be completed or initiated.
-
C.
hasPlanningConstraint
chosen
Indicates that there is a rule, limitation, or condition that must be considered when planning or scheduling an activity, resource, or process.
-
D.
startDateConstraint
Indicates a restriction or condition placed on when something is allowed to start, typically specifying valid or required start dates.
-
E.
hasRecreationConstraint
Indicates a restriction or limitation placed on how recreation or leisure activities may occur or be used.
- F. None of above.
Provenance (3 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 29, 2026, 9:03 p.m.