Triple
T26201633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Courts of Pakistan |
E655243
|
entity |
| Predicate | removalOfJudgesBy |
P160037
|
FINISHED |
| Object | Supreme Judicial Council of Pakistan |
—
|
NE NERFINISHED |
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: Supreme Judicial Council of Pakistan | Statement: [High Courts of Pakistan, removalOfJudgesBy, Supreme Judicial Council of Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removalOfJudgesBy Context triple: [High Courts of Pakistan, removalOfJudgesBy, Supreme Judicial Council of Pakistan]
-
A.
judgesReappointment
Indicates that a judge is being considered for or undergoing a process of reappointment to their judicial position.
-
B.
judgesElected
Indicates that the judges in question attained their positions through an electoral process rather than by appointment or other means.
-
C.
workedAsJudgeOn
Indicates that a person served in the role of a judge in connection with a particular case, court, or judicial proceeding.
-
D.
hasJudges
Indicates that one entity serves as a judge or panel of judges for another entity, such as an event, competition, or legal case.
-
E.
judgesAre
Indicates that one entity serves as a judge or evaluator of another entity.
- F. None of above. chosen
Provenance (4 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60cdba6248190b34176bc568e7697 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:48 p.m.