Triple

T35348202
Position Surface form Disambiguated ID Type / Status
Subject WS Society E1020800 entity
Predicate hasMemberType P121 FINISHED
Object Writer to the Signet
A Writer to the Signet is a Scottish solicitor qualified to practice law and traditionally associated with the Society of Writers to His Majesty’s Signet in Edinburgh.
E2137309 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: Writer to the Signet | Statement: [WS Society, hasMemberType, Writer to the Signet]
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: Writer to the Signet
Triple: [WS Society, hasMemberType, Writer to the Signet]
Generated description
A Writer to the Signet is a Scottish solicitor qualified to practice law and traditionally associated with the Society of Writers to His Majesty’s Signet in Edinburgh.

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_69f76decd95c8190ae428f6a19d535de completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f791913a3081908b9fc0de3fc88d5d completed May 3, 2026, 6:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3823d20e5c8190b2931c923f920909 completed June 21, 2026, 5:48 p.m.
NEDg Description generation batch_6a3824823190819085d090f2dbb608f9 completed June 21, 2026, 5:50 p.m.
NED2 Entity disambiguation (via description) batch_6a38266c9a8c81908c041eab45f05c6f completed June 21, 2026, 5:59 p.m.
Created at: May 3, 2026, 4:03 p.m.