Triple

T30800984
Position Surface form Disambiguated ID Type / Status
Subject George Douglas, 1st Earl of Dumbarton E784368 entity
Predicate givenName P17 FINISHED
Object George
George Douglas, 1st Earl of Dumbarton, was a 17th-century Scottish nobleman and soldier who served as a senior military commander under King James II of England.
E1934104 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: George | Statement: [George Douglas, 1st Earl of Dumbarton, givenName, George]
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: George
Triple: [George Douglas, 1st Earl of Dumbarton, givenName, George]
Generated description
George Douglas, 1st Earl of Dumbarton, was a 17th-century Scottish nobleman and soldier who served as a senior military commander under King James II of England.

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_69f224b3a7ec819096939414d103e31e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f6903a89c0819085dec72c68a5443d completed May 3, 2026, midnight
NED1 Entity disambiguation (via context triple) batch_6a28bbd7ecec8190a0e23d9e10aa308d completed June 10, 2026, 1:20 a.m.
NEDg Description generation batch_6a28bed0d2b081908ce9b83837a52b07 completed June 10, 2026, 1:33 a.m.
NED2 Entity disambiguation (via description) batch_6a28bf6bf59081908328d74d9623314e completed June 10, 2026, 1:35 a.m.
Created at: April 29, 2026, 8:42 p.m.