Triple

T36034215
Position Surface form Disambiguated ID Type / Status
Subject Strathclyde Police E1042352 entity
Predicate hadSpecialUnit P1198 FINISHED
Object public order unit
A public order unit is a specialized police team trained and equipped to manage large crowds, protests, and civil disturbances while maintaining public safety and order.
E2166944 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: public order unit | Statement: [Strathclyde Police, hadSpecialUnit, public order unit]
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: public order unit
Triple: [Strathclyde Police, hadSpecialUnit, public order unit]
Generated description
A public order unit is a specialized police team trained and equipped to manage large crowds, protests, and civil disturbances while maintaining public safety and order.

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_69f76e2d7e8c8190bac4e90734566799 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7ad1a1be8819081dd0f9d41bf54a0 completed May 3, 2026, 8:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38cb930a848190bcec41980d2f4d4a completed June 22, 2026, 5:43 a.m.
NEDg Description generation batch_6a38cd0a7b708190afd70d66d8aa7d6d completed June 22, 2026, 5:50 a.m.
NED2 Entity disambiguation (via description) batch_6a38cd8cf4708190a141ec08f61a6087 completed June 22, 2026, 5:52 a.m.
Created at: May 3, 2026, 4:07 p.m.