Triple
T10289710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morocco |
E241329
|
entity |
| Predicate | constitutionalStatusOfAmazigh |
P70272
|
FINISHED |
| Object | official language |
—
|
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: official language | Statement: [Morocco, constitutionalStatusOfAmazigh, official language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constitutionalStatusOfAmazigh Context triple: [Morocco, constitutionalStatusOfAmazigh, official language]
-
A.
legalStatusInAlgeria
Indicates the legal status or standing that an entity holds under the laws and regulations of Algeria.
-
B.
statusOfAzawadClaim
Indicates the current state or condition of a claim regarding the political or territorial status of Azawad.
-
C.
statusInMauritania
Indicates the legal, social, or conservation status that an entity holds specifically within the context of Mauritania.
-
D.
hasConstitutionalStatus
Indicates that an entity possesses a particular status, role, or recognition as defined or protected by a constitution or constitutional framework.
-
E.
constitutionStatus
chosen
Indicates the legal or formal status of an entity as defined or recognized by a constitution.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f117708190928f92ae2611d724 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:41 a.m.