Triple

T24370780
Position Surface form Disambiguated ID Type / Status
Subject British South Africa Police E614324 entity
Predicate shortName P43 FINISHED
Object BSAP
The BSAP, or British South Africa Police, was the colonial paramilitary police force of Southern Rhodesia (later Zimbabwe), combining law enforcement with military functions during British rule.
E1633149 NE 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: BSAP | Statement: [British South Africa Police, shortName, BSAP]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: BSAP
Triple: [British South Africa Police, shortName, BSAP]
Generated description
The BSAP, or British South Africa Police, was the colonial paramilitary police force of Southern Rhodesia (later Zimbabwe), combining law enforcement with military functions during British rule.

Provenance (5 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_69e2d7e1e010819098b95eb3f905943d completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2938b95188190b8f7ee1098c6088a completed April 29, 2026, 11:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0fd67560e081908086e1c79921a949 completed May 22, 2026, 4:07 a.m.
NEDg Description generation batch_6a0fd73ea7d88190b9bd774def308d97 completed May 22, 2026, 4:10 a.m.
NED2 Entity disambiguation (via description) batch_6a0fdb3919fc8190a66f585aff4e7570 completed May 22, 2026, 4:27 a.m.
Created at: April 18, 2026, 2:01 a.m.