Triple

T8000514
Position Surface form Disambiguated ID Type / Status
Subject Lord Grenville E186236 entity
Predicate familyName P18 FINISHED
Object Grenville E678322 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: Grenville | Statement: [Lord Grenville, familyName, Grenville]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Grenville
Context triple: [Lord Grenville, familyName, Grenville]
  • A. Grenville
    Grenville is a masculine given name most notably borne by American Civil War general and railroad engineer Grenville M. Dodge.
  • B. Grenville chosen
    Grenville was a former county-level jurisdiction in Ontario, Canada, that later became part of the combined Leeds and Grenville administrative region.
  • C. Townshend
    Townshend is an English surname historically associated with a prominent aristocratic family involved in British politics and public life.
  • D. Palliser
    Palliser is the aristocratic family name at the center of Anthony Trollope’s political and social novels, notably the Palliser series.
  • E. Schomberg
    Schomberg is a German-origin surname historically associated with notable European military leaders and nobility, including figures who served in the armies of several countries.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca82aaaf24819084b94d18f699ba53 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3c9b67988190a8a4a2c960017400 completed March 31, 2026, 3:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbe114372c819086f06e184d5ebde2 completed March 31, 2026, 2:58 p.m.
Created at: March 30, 2026, 5:17 p.m.