Triple
T25447198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Police Service of Kenya |
E637667
|
entity |
| Predicate | rankOfHead |
P158529
|
FINISHED |
| Object | Inspector General |
—
|
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: Inspector General | Statement: [National Police Service of Kenya, rankOfHead, Inspector General]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankOfHead Context triple: [National Police Service of Kenya, rankOfHead, Inspector General]
-
A.
rankIn
Indicates the relative position or level an entity holds within an ordered set, hierarchy, or competitive context.
-
B.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
C.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
-
D.
rankedAs
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
-
E.
rankIndicated
Indicates that one entity specifies, denotes, or reveals the hierarchical rank or level 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f70455f48190b23c09dbed884015 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 2:02 p.m.