Triple

T23566233
Position Surface form Disambiguated ID Type / Status
Subject Lord Mansfield E579376 entity
Predicate knownFor P22 FINISHED
Object Blachford v Preston
Blachford v Preston is an 18th-century English common law case notable for Lord Mansfield’s influential judgment helping to shape modern commercial and contract law principles.
E1596578 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: Blachford v Preston | Statement: [Lord Mansfield, knownFor, Blachford v Preston]
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: Blachford v Preston
Triple: [Lord Mansfield, knownFor, Blachford v Preston]
Generated description
Blachford v Preston is an 18th-century English common law case notable for Lord Mansfield’s influential judgment helping to shape modern commercial and contract law principles.

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_69e245fe24588190888f3aec8407d8e3 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f1af6c2930819090bc2b95725fbf18 completed April 29, 2026, 7:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f4565a7b4819085ebb7e7cd516d41 completed May 21, 2026, 5:48 p.m.
NEDg Description generation batch_6a0f49416f348190909aa4b99389c9d7 completed May 21, 2026, 6:04 p.m.
NED2 Entity disambiguation (via description) batch_6a0f4a15867c8190ba3268c241754707 completed May 21, 2026, 6:08 p.m.
Created at: April 17, 2026, 6:35 p.m.