Triple
T6668450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Moroccan Amazigh |
E151663
|
entity |
| Predicate | introducedInEducation |
P61242
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Standard Moroccan Amazigh, introducedInEducation, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInEducation Context triple: [Standard Moroccan Amazigh, introducedInEducation, 2003]
-
A.
introducedEducationSystem
Indicates that an entity established or brought a particular education system into use for another entity or context.
-
B.
usedInEducationIn
Indicates that something is employed or applied within educational contexts in a particular place or institution.
-
C.
firstTaughtIn
chosen
Indicates the time or place at which something (such as a concept, subject, or course) was initially taught or introduced in an instructional context.
-
D.
introducedAsGrade
Indicates that one entity was presented or designated to another specifically in the role or capacity of a particular grade or level.
-
E.
educationUse
Indicates the use or application of something specifically for educational purposes or in an educational context.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.