Triple

T24760246
Position Surface form Disambiguated ID Type / Status
Subject Thomas Fairfax, 2nd Lord Fairfax of Cameron E619414 entity
Predicate hasGivenName P17 FINISHED
Object Thomas
Thomas is the given name of Thomas Fairfax, 2nd Lord Fairfax of Cameron, a prominent Parliamentarian general during the English Civil War.
E619414 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: Thomas | Statement: [Thomas Fairfax, 2nd Lord Fairfax of Cameron, hasGivenName, Thomas]
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: Thomas
Triple: [Thomas Fairfax, 2nd Lord Fairfax of Cameron, hasGivenName, Thomas]
Generated description
Thomas is the given name of Thomas Fairfax, 2nd Lord Fairfax of Cameron, a prominent Parliamentarian general during the English Civil War.

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_69e2fabbea94819092ed41348909622f completed April 18, 2026, 3:30 a.m.
NER Named-entity recognition batch_69f4107b385481908ed34c8c4dc90c45 completed May 1, 2026, 2:31 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1032ff16748190a25710b73254416c completed May 22, 2026, 10:42 a.m.
NEDg Description generation batch_6a10341e764c819083c10e4d151da1c6 completed May 22, 2026, 10:46 a.m.
NED2 Entity disambiguation (via description) batch_6a1034d8d52481908c5c422f943c683b completed May 22, 2026, 10:50 a.m.
Created at: April 18, 2026, 4:27 a.m.