Triple

T27919092
Position Surface form Disambiguated ID Type / Status
Subject ANDSF E706154 entity
Predicate hasPart P35 FINISHED
Object Afghan Uniform Police
The Afghan Uniform Police was a branch of Afghanistan’s national police force responsible for general law enforcement, public order, and security in urban and rural areas.
E34439 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: Afghan Uniform Police | Statement: [ANDSF, hasPart, Afghan Uniform Police]
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: Afghan Uniform Police
Triple: [ANDSF, hasPart, Afghan Uniform Police]
Generated description
The Afghan Uniform Police was a branch of Afghanistan’s national police force responsible for general law enforcement, public order, and security in urban and rural areas.

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_69ef96b6cc808190aab19fb18b235f4b completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f63a5c15fc8190b1b80d2469bbffe9 completed May 2, 2026, 5:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a15c8ee6fb881909e699609455491e3 completed May 26, 2026, 4:23 p.m.
NEDg Description generation batch_6a15ca6352088190896197841a36baa7 completed May 26, 2026, 4:29 p.m.
NED2 Entity disambiguation (via description) batch_6a15ccdad0d0819093ee0e177574c96d completed May 26, 2026, 4:39 p.m.
Created at: April 27, 2026, 6:55 p.m.