Triple
T38461980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabinet Committee on Institutional Reforms |
E912474
|
entity |
| Predicate | decisionsApprovedBy |
P73913
|
FINISHED |
| Object | Federal Cabinet 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: Federal Cabinet of Pakistan | Statement: [Cabinet Committee on Institutional Reforms, decisionsApprovedBy, Federal Cabinet of Pakistan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionsApprovedBy Context triple: [Cabinet Committee on Institutional Reforms, decisionsApprovedBy, Federal Cabinet of Pakistan]
-
A.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
B.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
C.
decisionsTakenBy
chosen
Indicates that one or more decisions are made or taken by a specified agent or entity.
-
D.
approvedAs
Indicates that one entity has been officially accepted, authorized, or validated in a particular role, status, or capacity by another entity.
-
E.
someMembersApprovedBy
Indicates that at least one member of a group has given approval for the associated entity or action.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.