Triple
T31594353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nomocanon of Ibn al-ʿAssal |
E806181
|
entity |
| Predicate | typeOfSourceFor |
P109994
|
FINISHED |
| Object | Ethiopian imperial law |
—
|
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: Ethiopian imperial law | Statement: [Nomocanon of Ibn al-ʿAssal, typeOfSourceFor, Ethiopian imperial law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSourceFor Context triple: [Nomocanon of Ibn al-ʿAssal, typeOfSourceFor, Ethiopian imperial law]
-
A.
hasTypeOfSource
chosen
Indicates that one entity is classified as a particular kind or category of source in relation to another entity.
-
B.
detectedSourceType
Indicates the type or category of source from which something was detected.
-
C.
classifiesSource
Indicates that an entity assigns or determines the category or type of a given source.
-
D.
traitSourceFor
Indicates that one entity serves as the origin or provider of a particular trait or characteristic for another entity.
-
E.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffed8912488190baa05f572e5b1b89 |
completed | May 10, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69ffed12a76c8190ad85c6ac869c72e9 |
completed | May 10, 2026, 2:27 a.m. |
Created at: April 30, 2026, 10:29 p.m.