Triple
T21573947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukhtaṣar Khalīl |
E532349
|
entity |
| Predicate | statusInMaghrib |
P144313
|
FINISHED |
| Object | standard Maliki manual |
—
|
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: standard Maliki manual | Statement: [Mukhtaṣar Khalīl, statusInMaghrib, standard Maliki manual]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInMaghrib Context triple: [Mukhtaṣar Khalīl, statusInMaghrib, standard Maliki manual]
-
A.
statusInMauritania
Indicates the legal, social, or conservation status that an entity holds specifically within the context of Mauritania.
-
B.
scriptStatusInMorocco
Indicates the status or condition of a script as it exists or is used within the context of Morocco.
-
C.
statusInMali
Indicates the legal, social, or official condition or standing that an entity holds within the context of Mali.
-
D.
MoroccanStrengthApprox
Indicates an approximate assessment or estimation of the strength associated with Morocco or Moroccan-related entities.
-
E.
statusInEgypt
Indicates the legal, social, or official condition or standing that an entity holds specifically within the context of Egypt.
- F. None of above. chosen
Provenance (4 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cef2748190990a81967d49b706 |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:30 p.m.