Triple
T25377802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maghreb Bank for Investment and Foreign Trade |
E633099
|
entity |
| Predicate | fullNameInArabic |
P6450
|
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: [Maghreb Bank for Investment and Foreign Trade, fullNameInArabic, المصرف المغاربي للاستثمار والتجارة الخارجية]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullNameInArabic Context triple: [Maghreb Bank for Investment and Foreign Trade, fullNameInArabic, المصرف المغاربي للاستثمار والتجارة الخارجية]
-
A.
hasGivenNameFormInArabic
Indicates that an entity has a specific given-name form expressed in the Arabic language.
-
B.
hasNameInArabic
chosen
Indicates that an entity is associated with a specific name expressed in the Arabic language.
-
C.
nameInAramaic
Indicates that an entity has a specific name expressed in the Aramaic language.
-
D.
nameInMiddlePersian
Indicates that an entity is referred to by a particular name when expressed in the Middle Persian language.
-
E.
toponymInArabic
Indicates that a place name is given in its Arabic-language form.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f55e5d7e2c8190937af482e50e6cad |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:38 p.m.