Triple
T14052520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakistan Administrative Service |
E338125
|
entity |
| Predicate | officersKnownAs |
P112638
|
FINISHED |
| Object | PAS officers |
—
|
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: PAS officers | Statement: [Pakistan Administrative Service, officersKnownAs, PAS officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officersKnownAs Context triple: [Pakistan Administrative Service, officersKnownAs, PAS officers]
-
A.
officersAre
Indicates that certain individuals hold the role or position of officers within a specified group, organization, or context.
-
B.
officersServeAs
Indicates that certain individuals hold and perform the role or duties of officers within a particular organization or context.
-
C.
policeCharacter
Indicates that one entity serves as a police officer or law-enforcement figure in relation to another entity.
-
D.
officerCategory
Indicates the classification or type of officer role that an individual holds within an organization or system.
-
E.
commissionsOfficersFor
Indicates that an authority or organization formally appoints or authorizes individuals to serve as officers.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c8bc54c8190a12f0fc056568538 |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:20 p.m.