Triple

T35667255
Position Surface form Disambiguated ID Type / Status
Subject James Douglas, 3rd Earl of Morton E1030605 entity
Predicate title P38 FINISHED
Object 3rd Earl of Morton
The 3rd Earl of Morton was a Scottish nobleman of the powerful Douglas family who played a significant role in 16th-century Scottish politics.
E2165796 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 Morton | Statement: [James Douglas, 3rd Earl of Morton, title, 3rd Earl of Morton]
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 Morton
Triple: [James Douglas, 3rd Earl of Morton, title, 3rd Earl of Morton]
Generated description
The 3rd Earl of Morton was a Scottish nobleman of the powerful Douglas family who played a significant role in 16th-century Scottish politics.

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_69f76e0acfc0819082c8495c2210ce73 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79fae59588190bf0de193783c5de2 completed May 3, 2026, 7:19 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38bfbe46e48190b633534afcffa296 completed June 22, 2026, 4:53 a.m.
NEDg Description generation batch_6a38c24c230c81909f01f91aefcf46a4 completed June 22, 2026, 5:04 a.m.
NED2 Entity disambiguation (via description) batch_6a38c2a42c4c8190a84a0beee4e5cf45 completed June 22, 2026, 5:05 a.m.
Created at: May 3, 2026, 4:05 p.m.