Triple
T36561582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سلطان المغرب |
E901851
|
entity |
| Predicate | الشرعية_التقليدية |
P17298
|
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.
uniformTradition
Indicates that multiple entities follow the same established customs, practices, or conventions in a consistent manner.
-
B.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
-
C.
hasLawTradition
chosen
Indicates that one legal system, jurisdiction, or entity follows or is based on a particular legal tradition or family of law.
-
D.
governedWithinTradition
Indicates that an entity’s actions, decisions, or organization are regulated or constrained according to a particular established tradition or customary framework.
-
E.
governedTraditionallyBy
Indicates that one entity has historically exercised customary or long-established governing authority over another entity.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.