Triple

T1058594
Position Surface form Disambiguated ID Type / Status
Subject William O. Douglas E22853 entity
Predicate familyName P18 FINISHED
Object Douglas E80 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: Douglas | Statement: [William O. Douglas, familyName, Douglas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Douglas
Context triple: [William O. Douglas, familyName, Douglas]
  • A. Douglas
    Douglas is a small lakeside city in Allegan County, Michigan, known for its arts community and proximity to Lake Michigan beaches.
  • B. Douglas chosen
    Douglas is a masculine given name of Scottish origin that has been widely used in English-speaking countries.
  • C. Douglas
    Douglas is the capital and largest town of the Isle of Man, serving as its main commercial center and principal ferry port.
  • D. Avondale
    Avondale is a well-known residential and commercial suburb of Harare, Zimbabwe, noted for its shopping centers and relatively affluent character.
  • E. Dixon
    Dixon is a small agricultural city in Northern California known historically for sheep ranching and its annual May Fair.
  • 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_69a493dada0481909c43649f9843ea91 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b8dc9e8c819099fbb192bcf80615 completed March 1, 2026, 10:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac6f0a15e48190a011c4aff5c285af completed March 7, 2026, 6:31 p.m.
Created at: March 1, 2026, 7:42 p.m.