Triple
T34455386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | المجادلة |
E884489
|
entity |
| Predicate | محورها التشريعي |
P170214
|
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.
محور تشريعي
chosen
Indicates a legislative axis or focus around which lawmaking activities, policies, or legal reforms are organized or structured.
-
B.
محورها التعبدي
Indicates that something is centered on or characterized by an aspect of worship or devotional practice.
-
C.
محور عقدي
Indicates a doctrinal or ideological axis around which beliefs, positions, or alignments are organized and structured.
-
D.
legislativeMechanism
Indicates a relationship where a law, policy, or rule is created, modified, or enacted through a specific formal legislative process or procedure.
-
E.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71976c49c8190943046a0ff8950cb |
completed | May 3, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.