Triple
T12276526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharia Court of Appeal of the Federal Capital Territory |
E292602
|
entity |
| Predicate | hasJudgesCalled |
P42992
|
FINISHED |
| Object | Kadīs |
—
|
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: Kadīs | Statement: [Sharia Court of Appeal of the Federal Capital Territory, hasJudgesCalled, Kadīs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJudgesCalled Context triple: [Sharia Court of Appeal of the Federal Capital Territory, hasJudgesCalled, Kadīs]
-
A.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
B.
hasJudgesRole
chosen
Indicates that an entity serves in the capacity or role of a judge within a specified context or system.
-
C.
statusInJudges
Indicates that an entity holds a particular role, position, or standing within a group or body of judges.
-
D.
hasJurors
Indicates that one entity serves as or includes jurors in relation to another entity, typically in the context of a legal case or proceeding.
-
E.
judgesMayBe
Indicates that certain individuals can serve in the role of judges under specified conditions or classifications.
- 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_69d6ab6856488190b5d31178d5015f8e |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9380a5e78819086bd4dfe9a83d1f5 |
completed | April 10, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69d91c4a66cc819083ce6fcaf5042af6 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.