Triple
T36561585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | سلطان المغرب |
E901851
|
entity |
| Predicate | أشهر_السلالات_الحديثة_المرتبطة |
P12229
|
FINISHED |
| Object | العلويون |
—
|
NE NERFINISHED |
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.
associatedDynasticOrder
Indicates a relationship where an entity is linked to, or formally connected with, a particular dynastic order.
-
B.
notableDynastyEmergingFrom
Indicates that a notable or historically significant dynasty originated from or arose out of a specified source, such as a place, group, or earlier lineage.
-
C.
dynastyAlsoKnownAs
Indicates that a dynasty is referred to by an alternative name, alias, or variant designation.
-
D.
lastReigningDynastyOf
Indicates that one dynasty is the final ruling dynasty to have governed a particular political entity or territory.
-
E.
modernAssociation
chosen
Indicates a contemporary or currently relevant connection, affiliation, or relationship between entities.
- 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.