Triple
T25944255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | المحكمة الدستورية العليا |
E653794
|
entity |
| Predicate | تستند إلى |
P7125
|
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.
areBasedOn
Indicates that one entity is founded, derived, or developed from the principles, content, or structure of another entity.
-
B.
isBasedOn
chosen
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
-
C.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
-
D.
basedOnRequirementOf
Indicates that something is established, created, or determined according to a specified requirement or set of requirements.
-
E.
standingBasis
Indicates that one entity serves as the foundational reason, justification, or basis for another entity’s standing, status, or position in a given 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60462fad88190be275c21dabc791c |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f4a10480748190a2e67bd399fc435d |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 8:41 a.m.