Triple
T32413089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Shariat Court of Pakistan |
E828275
|
entity |
| Predicate | allowsPetitionsFrom |
P67728
|
FINISHED |
| Object | citizens of 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: citizens of Pakistan | Statement: [Federal Shariat Court of Pakistan, allowsPetitionsFrom, citizens of Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsPetitionsFrom Context triple: [Federal Shariat Court of Pakistan, allowsPetitionsFrom, citizens of Pakistan]
-
A.
canBePetitionedBy
chosen
Indicates that an entity is eligible to receive formal petitions, requests, or appeals from another entity.
-
B.
containsPetition
Indicates that one entity includes or holds a petition within it, either as content or as a component.
-
C.
numberOfPetitions
Indicates the total count of petitions associated with a given entity or context.
-
D.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
E.
admitsFrom
Indicates that one entity accepts or enrolls individuals coming from another specified source or institution.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 12:53 a.m.