Triple

T12014158
Position Surface form Disambiguated ID Type / Status
Subject John M. Harlan II E285980 entity
Predicate familyName P18 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: [John M. Harlan II, familyName, Harlan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Harlan
Context triple: [John M. Harlan II, familyName, 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_69d6ab45a368819084fce08bf0dc3705 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903d884488190b4450a98088208ef completed April 10, 2026, 2:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69f48b4535f48190ac5b2cabb4daf4af completed May 1, 2026, 11:15 a.m.
Created at: April 8, 2026, 9:46 p.m.