Triple
T9220598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | كسوة الكعبة |
E221348
|
entity |
| Predicate | تخضع لـ |
P1313
|
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: [كسوة الكعبة, تخضع لـ, معايير عالية في اختيار الخيوط]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: تخضع لـ Context triple: [كسوة الكعبة, تخضع لـ, معايير عالية في اختيار الخيوط]
-
A.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
B.
holdsUnder
Indicates that one entity maintains possession, control, or validity of another entity subject to certain conditions, constraints, or a specific context.
-
C.
susceptibleTo
Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
-
D.
subjectToRegulation
Indicates that an entity is governed, constrained, or controlled by a specific rule, law, or regulatory framework.
-
E.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda75b6888190814cfb890e763b8f |
completed | April 1, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:28 p.m.