Triple
T29383977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somali judiciary |
E745203
|
entity |
| Predicate | usesLegalSource |
P65906
|
FINISHED |
| Object | Somali statutory 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: Somali statutory law | Statement: [Somali judiciary, usesLegalSource, Somali statutory law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLegalSource Context triple: [Somali judiciary, usesLegalSource, Somali statutory law]
-
A.
usesLegalCode
Indicates that one entity applies, references, or operates under a particular legal code in its actions or regulations.
-
B.
majorLegalSource
chosen
Indicates that one entity serves as a primary or authoritative legal basis or reference for another entity.
-
C.
usesLegalPrecedentFrom
Indicates that one legal case, decision, or argument relies on, cites, or is based upon the legal precedent established by another.
-
D.
usesLawTo
Indicates that one entity applies or relies on a specific law as a means or tool to affect, regulate, or influence another entity or situation.
-
E.
usesLegalMethod
Indicates that an action or process is carried out using methods that comply with applicable laws and legal standards.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 2:37 p.m.