Triple

T3864
Position Surface form Disambiguated ID Type / Status
Subject Hudson River E73 entity
Predicate namedAfter P63 FINISHED
Object Henry Hudson E525 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: Henry Hudson | Statement: [Hudson River, namedAfter, Henry Hudson]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Henry Hudson
Context triple: [Hudson River, namedAfter, Henry Hudson]
  • A. Henry Hudson chosen
    Henry Hudson was an English sea explorer and navigator of the early 17th century best known for his voyages in search of a northwest passage and for lending his name to the Hudson River and Hudson Bay.
  • B. Edwin
    Edwin is a masculine given name of Old English origin meaning "rich friend" or "prosperous friend."
  • C. Harold Hazen
    Harold Hazen was an American electrical engineer and MIT professor known for his pioneering work in control systems and his role in developing early analog computing devices.
  • D. John Harvard
    John Harvard was a 17th-century English clergyman and benefactor whose substantial bequest helped establish the institution that became Harvard University.
  • E. Pierre Charles L’Enfant
    Pierre Charles L’Enfant was a French-born American architect and civil engineer best known for creating the original plan for the city of Washington, D.C.
  • 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_69a238d6b47881909e68288aed2fd858 completed Feb. 28, 2026, 12:37 a.m.
NER Named-entity recognition batch_69a2399c646c8190b4977ed56b8835a8 completed Feb. 28, 2026, 12:41 a.m.
NED1 Entity disambiguation (via context triple) batch_69a243c6f10c81908305b9e03c79a6ae completed Feb. 28, 2026, 1:24 a.m.
Created at: Feb. 28, 2026, 12:40 a.m.