Triple
T9526497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fetha Nagast |
E229772
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Ethiopian legal text |
C21846
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Ethiopian legal text Context triple: [Fetha Nagast, instanceOf, Ethiopian legal text]
-
A.
historical legal text
chosen
A historical legal text is a written document from a past era that records laws, legal decisions, or legal reasoning, reflecting the legal norms, institutions, and societal values of its time.
-
B.
African Union legal instrument
An African Union legal instrument is a formal, binding or non-binding document adopted by AU organs that establishes norms, rights, obligations, or procedures applicable to member states and AU institutions within the Union’s legal framework.
-
C.
scripture of Ethiopian Jews
The scripture of Ethiopian Jews, known as the Orit, is a Ge'ez-language canon that includes the Torah and other biblical and apocryphal books, reflecting a distinct Jewish tradition shaped in isolation from Rabbinic Judaism.
-
D.
figure in Ethiopian tradition
A figure in Ethiopian tradition is a culturally significant personage—real, legendary, or symbolic—who embodies the values, beliefs, and historical memory of Ethiopian society through stories, rituals, and artistic representations.
-
E.
Ge'ez-language term
A Ge'ez-language term is a lexical item originating from the classical Ethiopic language Ge'ez, used historically in liturgy, literature, and scholarship within the Ethiopian and Eritrean cultural spheres.
- F. None of above.
Provenance (1 batch)
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_69ca847870a881909d8d751a7d29da39 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 7:59 p.m.