Triple

T28450633
Position Surface form Disambiguated ID Type / Status
Subject Cabinet Secretary (United Kingdom) E716567 entity
Predicate officeHoldersInclude P537 FINISHED
Object Simon Case
Simon Case is a senior British civil servant who has served as the United Kingdom's Cabinet Secretary and Head of the Civil Service.
E1818381 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: Simon Case | Statement: [Cabinet Secretary (United Kingdom), officeHoldersInclude, Simon Case]
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: Simon Case
Triple: [Cabinet Secretary (United Kingdom), officeHoldersInclude, Simon Case]
Generated description
Simon Case is a senior British civil servant who has served as the United Kingdom's Cabinet Secretary and Head of the Civil Service.

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_69efd6b76f8c8190a7ba908aca280942 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f64e71a1808190afe91d850046e923 completed May 2, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_6a16418b76748190a3f56aeb6b39eb7b completed May 27, 2026, 12:57 a.m.
NEDg Description generation batch_6a1641ea230081909386490abb2dfef9 completed May 27, 2026, 12:59 a.m.
NED2 Entity disambiguation (via description) batch_6a1642cb54248190a5245bbf55464025 completed May 27, 2026, 1:03 a.m.
Created at: April 28, 2026, 1:51 a.m.