Triple

T21945555
Position Surface form Disambiguated ID Type / Status
Subject Jim Sheridan E541923 entity
Predicate familyName P18 FINISHED
Object Sheridan 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: Sheridan | Statement: [Jim Sheridan, familyName, Sheridan]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sheridan
Context triple: [Jim Sheridan, familyName, Sheridan]
  • A. Sheridan chosen
    Sheridan is a surname of Irish origin borne by numerous notable figures in politics, the military, arts, and entertainment.
  • B. Sheridan
    Sheridan is a residential neighbourhood in Mississauga, Ontario, known for its suburban character and proximity to major commercial and educational hubs.
  • C. Larimore
    Larimore is a small city in eastern North Dakota, United States, known for its rural character and proximity to Grand Forks.
  • D. Winfield
    Winfield is a small town located in Lake County, Indiana, known primarily as a residential community near the Chicago metropolitan area.
  • E. Winfield
    Winfield is a masculine given name most notably borne by 19th-century American military leader Winfield Scott.
  • 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_69e0c47ef0e48190a50e1bcc43f4b3fd completed April 16, 2026, 11:14 a.m.
NER Named-entity recognition batch_69f12427c2b48190949c41bd3be2d9f3 completed April 28, 2026, 9:18 p.m.
Created at: April 16, 2026, 7:57 p.m.