Triple

T34903258
Position Surface form Disambiguated ID Type / Status
Subject Hugh Campbell, 3rd Earl of Loudoun E1006649 entity
Predicate positionHeld P8 FINISHED
Object 3rd Earl of Loudoun
The 3rd Earl of Loudoun, Hugh Campbell, was a Scottish nobleman and peer active in the late 17th and early 18th centuries.
E2157440 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: 3rd Earl of Loudoun | Statement: [Hugh Campbell, 3rd Earl of Loudoun, positionHeld, 3rd Earl of Loudoun]
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: 3rd Earl of Loudoun
Triple: [Hugh Campbell, 3rd Earl of Loudoun, positionHeld, 3rd Earl of Loudoun]
Generated description
The 3rd Earl of Loudoun, Hugh Campbell, was a Scottish nobleman and peer active in the late 17th and early 18th centuries.

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_69f76dc1b4a081909b4c6e4d8ec0aa2d completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f781ea02c881909b0fe83ee1550a0e completed May 3, 2026, 5:12 p.m.
NED1 Entity disambiguation (via context triple) batch_6a389bf8b3788190aa0552efef4762c9 completed June 22, 2026, 2:20 a.m.
NEDg Description generation batch_6a389ca938d0819094ce32b9a0ca8aa3 completed June 22, 2026, 2:23 a.m.
NED2 Entity disambiguation (via description) batch_6a389d7b23748190993070e1405d79de completed June 22, 2026, 2:27 a.m.
Created at: May 3, 2026, 4 p.m.