Triple

T34319760
Position Surface form Disambiguated ID Type / Status
Subject Thomas Wilde, 1st Baron Truro E880700 entity
Predicate nobleTitle P914 FINISHED
Object Baron Truro
Baron Truro is a British peerage title created in the 19th century for the lawyer and politician Thomas Wilde, who served as Lord Chancellor of Great Britain.
E2094019 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: Baron Truro | Statement: [Thomas Wilde, 1st Baron Truro, nobleTitle, Baron Truro]
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: Baron Truro
Triple: [Thomas Wilde, 1st Baron Truro, nobleTitle, Baron Truro]
Generated description
Baron Truro is a British peerage title created in the 19th century for the lawyer and politician Thomas Wilde, who served as Lord Chancellor of Great Britain.

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_69f349b9cd508190a996a616903b3e6d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f7136dd6fc8190b6db5f4458a564f0 completed May 3, 2026, 9:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a3704907b908190b92dd393478d232e completed June 20, 2026, 9:22 p.m.
NEDg Description generation batch_6a370646acf48190bfcfa72a28f0f117 completed June 20, 2026, 9:29 p.m.
NED2 Entity disambiguation (via description) batch_6a3706d092248190bc836c78f01deb84 completed June 20, 2026, 9:32 p.m.
Created at: May 1, 2026, 1:57 a.m.