Triple

T6793126
Position Surface form Disambiguated ID Type / Status
Subject Richard S. Ewell E155984 entity
Predicate familyName P18 FINISHED
Object Ewell E17357 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: Ewell | Statement: [Richard S. Ewell, familyName, Ewell]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ewell
Context triple: [Richard S. Ewell, familyName, Ewell]
  • A. Ewell chosen
    Ewell is a suburban town in the borough of Epsom and Ewell in Surrey, England, known for its historic village center and proximity to London.
  • B. Ewell
    Ewell is a small, remote waterfront community on Smith Island in the Chesapeake Bay, known for its crabbing heritage and traditional island culture.
  • C. Lorton
    Lorton is a small village and civil parish in Cumbria, England, situated in the scenic Lake District near the town of Cockermouth.
  • D. Lorton
    Lorton is a suburban community in Fairfax County, Northern Virginia, known for its residential neighborhoods, proximity to major transportation routes, and redevelopment of the former Lorton Reformatory site.
  • E. Ludwell
    Ludwell is an English-origin surname historically associated with colonial Virginia families and figures such as Hannah Harrison Ludwell.
  • 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_69c6881844448190a65822d9b39d7f88 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d2af6f908190809e39b73894e513 completed March 27, 2026, 6:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69c71a8eaefc819098e848b3012da749 completed March 28, 2026, 12:02 a.m.
Created at: March 27, 2026, 2:15 p.m.