Triple

T26220482
Position Surface form Disambiguated ID Type / Status
Subject Crown Jeweller E655750 entity
Predicate notableOfficeHolder P5750 FINISHED
Object Mark Appleby
Mark Appleby is a British jeweller who served as Crown Jeweller to the British royal family, responsible for the maintenance and preparation of the Crown Jewels.
E1721112 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: Mark Appleby | Statement: [Crown Jeweller, notableOfficeHolder, Mark Appleby]
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: Mark Appleby
Triple: [Crown Jeweller, notableOfficeHolder, Mark Appleby]
Generated description
Mark Appleby is a British jeweller who served as Crown Jeweller to the British royal family, responsible for the maintenance and preparation of the Crown Jewels.

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_69ee5b4a77e08190bfcb5f8ecdc55abd completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f60d4f66748190819e060ab3dc492c completed May 2, 2026, 2:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a119a45a960819083e66a01ca05c074 completed May 23, 2026, 12:15 p.m.
NEDg Description generation batch_6a119b1444008190a4cdcbe5fd8bca98 completed May 23, 2026, 12:18 p.m.
NED2 Entity disambiguation (via description) batch_6a119c2d13388190869495b5b068ab15 completed May 23, 2026, 12:23 p.m.
Created at: April 26, 2026, 8:55 p.m.