Triple
T31098982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | رمي الجمرات |
E792617
|
entity |
| Predicate | hasMinimumQuantity |
P84417
|
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: [رمي الجمرات, hasMinimumQuantity, سبع حصيات لكل جمرة عند الجمهور]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMinimumQuantity Context triple: [رمي الجمرات, hasMinimumQuantity, سبع حصيات لكل جمرة عند الجمهور]
-
A.
hasMinimum
chosen
Indicates that an entity possesses at least a specified lower bound or smallest allowable value, quantity, or level in relation to another entity or constraint.
-
B.
hasMinimumLoadAmount
Indicates that there is a specified lowest allowable or required amount of load that must be met or exceeded.
-
C.
minimumQuantityTrigger
Indicates that a specified action or condition is triggered when the quantity of an item falls to or below a defined minimum threshold.
-
D.
hasMinimumWeight
Indicates that an entity’s weight meets or exceeds a specified minimum threshold.
-
E.
hasKeyQuantity
Indicates that an entity is associated with a primary or defining quantity that characterizes or measures it.
- 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_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 29, 2026, 9:03 p.m.