Triple
T7883747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Courts of Pakistan |
E183047
|
entity |
| Predicate | exercisePower |
P19487
|
FINISHED |
| Object | writ jurisdiction |
—
|
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: writ jurisdiction | Statement: [High Courts of Pakistan, exercisePower, writ jurisdiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exercisePower Context triple: [High Courts of Pakistan, exercisePower, writ jurisdiction]
-
A.
exercise
Indicates that an entity engages in physical activity or training, typically to improve health, fitness, or performance.
-
B.
exerciseOfPower
chosen
Indicates the exertion or application of authority, control, or influence by one entity over another or within a given context.
-
C.
participatesInExercise
Indicates that an entity takes part in a physical exercise activity or workout.
-
D.
freeExerciseTest
Indicates a legal assessment of whether a law or government action improperly burdens or restricts an individual’s or group’s free exercise of religion.
-
E.
strengthPeak
Indicates the point or period at which an entity’s strength reaches its maximum level.
- 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_69ca828af6e48190a06ee7010d8f0e64 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39d4d09481909a61037243397eff |
completed | March 31, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:58 p.m.