Triple

T30117282
Position Surface form Disambiguated ID Type / Status
Subject John Grey, 1st Earl of Tankerville E765454 entity
Predicate givenName P17 FINISHED
Object John
John Grey, 1st Earl of Tankerville, was an English nobleman and soldier of the early 15th century who held prominent titles and lands during the reign of King Henry V.
E1901243 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: John | Statement: [John Grey, 1st Earl of Tankerville, givenName, John]
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: John
Triple: [John Grey, 1st Earl of Tankerville, givenName, John]
Generated description
John Grey, 1st Earl of Tankerville, was an English nobleman and soldier of the early 15th century who held prominent titles and lands during the reign of King Henry V.

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_69f2247716748190ae4f16998f49ddf1 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f67de83980819098ac89078e1d75d6 completed May 2, 2026, 10:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a274c9e17bc8190ad45c636fce0d07a completed June 8, 2026, 11:13 p.m.
NEDg Description generation batch_6a274db4d6a88190a6c3cfbb05fa7320 completed June 8, 2026, 11:18 p.m.
NED2 Entity disambiguation (via description) batch_6a274e674bbc8190a88d0e74b663574a completed June 8, 2026, 11:21 p.m.
Created at: April 29, 2026, 7:12 p.m.