Triple
T7310395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attorney-General of Pakistan |
E168075
|
entity |
| Predicate | mayAppear |
P76230
|
FINISHED |
| Object | before any court in Pakistan |
—
|
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: before any court in Pakistan | Statement: [Attorney-General of Pakistan, mayAppear, before any court in Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAppear Context triple: [Attorney-General of Pakistan, mayAppear, before any court in Pakistan]
-
A.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
B.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
-
C.
apparentIn
Indicates that something is visibly present, manifested, or evident within or through another thing or context.
-
D.
mayResultIn
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
-
E.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebff866081909916796d1b72aee8 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 3:01 p.m.