Triple

T23195198
Position Surface form Disambiguated ID Type / Status
Subject Hudson Taylor E579853 entity
Predicate givenName P17 FINISHED
Object Hudson NE NERFINISHED

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: Hudson | Statement: [Hudson Taylor, givenName, Hudson]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hudson
Context triple: [Hudson Taylor, givenName, Hudson]
  • A. Hudson
    Hudson is a small historic city in Columbia County, New York, known for its revitalized downtown, arts scene, and 19th-century architecture along the Hudson River.
  • B. Hudson
    Hudson is a city in Summit County, Ohio, known for its historic downtown, affluent residential character, and strong public school system.
  • C. Hudson
    Hudson is a small town in Colorado, United States, located on the plains northeast of Denver.
  • D. Hudson chosen
    Hudson is a masculine given name of English origin, traditionally meaning "son of Hugh" and commonly used in English-speaking countries.
  • E. Hudson
    Hudson is a wise, battle-hardened elder gargoyle and former leader of the Manhattan Clan in the animated television series "Gargoyles."
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e24600eed08190bd7e5295653a1503 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18fda64cc8190aeb5ccd8d8d20858 completed April 29, 2026, 4:58 a.m.
Created at: April 17, 2026, 4:06 p.m.