Triple

T21445930
Position Surface form Disambiguated ID Type / Status
Subject Ford sewing machinists E529074 entity
Predicate location P40 FINISHED
Object Dagenham 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: Dagenham | Statement: [Ford sewing machinists, location, Dagenham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dagenham
Context triple: [Ford sewing machinists, location, Dagenham]
  • A. Dagenham chosen
    Dagenham is a suburban town in East London, historically known for its large Ford car plant and extensive post-war housing estates.
  • B. Rainham
    Rainham is a suburban town in East London, England, known for its residential character and proximity to the River Thames.
  • C. Hainault
    Hainault is a suburban area in northeast London, England, known for its residential character and proximity to Hainault Forest Country Park.
  • D. Sidcup
    Sidcup is a suburban district in southeast London, England, known for its residential character, local colleges, and position within the London Borough of Bexley.
  • E. Dartford
    Dartford is a historic market and industrial town in southeast England, situated on the River Darent and serving as a key commuter hub for London.
  • 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_69e0c457579481909db68053ed99750c completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e8b707ecd88190b3576b8923840870 completed April 22, 2026, 11:54 a.m.
Created at: April 16, 2026, 6:05 p.m.