Triple
T37444594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khyber Pakhtunkhwa Public Service Commission |
E930508
|
entity |
| Predicate | appliesMeritSystem |
P164083
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Khyber Pakhtunkhwa Public Service Commission, appliesMeritSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesMeritSystem Context triple: [Khyber Pakhtunkhwa Public Service Commission, appliesMeritSystem, true]
-
A.
hasSpecialMerit
Indicates that an entity possesses exceptional or noteworthy qualities that distinguish it from others in a positive way.
-
B.
awardSystem
Indicates a relationship where an entity establishes or uses a structured scheme for granting awards, honors, or recognitions to others.
-
C.
encouragedMeritocracy
chosen
Indicates that an entity promoted or supported a system in which individuals advance based on ability or merit rather than other factors.
-
D.
awardCriteria
Indicates the standards or conditions used to determine eligibility for receiving an award or recognition.
-
E.
usesNominationSystem
Indicates that an entity employs a nomination-based process to select or appoint candidates or participants.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:17 p.m.