Triple

T13023778
Position Surface form Disambiguated ID Type / Status
Subject Harlan Anderson E326246 entity
Predicate hasGivenName P17 FINISHED
Object Harlan E193721 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: Harlan | Statement: [Harlan Anderson, hasGivenName, Harlan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harlan
Context triple: [Harlan Anderson, hasGivenName, Harlan]
  • A. Harlan chosen
    Harlan is a masculine given name of English origin, historically associated with figures such as U.S. Chief Justice Harlan F. Stone.
  • B. De Witt
    De Witt is a Dutch surname most famously associated with Johan de Witt, a prominent 17th-century statesman of the Dutch Republic.
  • C. Andrew Harlan
    Andrew Harlan is the time-manipulating Technician protagonist of Isaac Asimov’s science fiction novel "The End of Eternity."
  • D. Hawley
    Hawley is a small borough in northeastern Pennsylvania known for its historic charm and proximity to the Pocono Mountains and Lake Wallenpaupack.
  • E. Hawley
    Hawley is an English-language surname borne by various notable individuals in politics, academia, and other fields.
  • 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_69d8076cc45c81908123123f43e69266 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d97ed05e9c8190a4f208662bca0602 completed April 10, 2026, 10:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6c11c1f6c8190be1c570a7e44a313 completed May 3, 2026, 3:29 a.m.
Created at: April 9, 2026, 8:52 p.m.