Triple

T8131205
Position Surface form Disambiguated ID Type / Status
Subject RSAF Enfield E189855 entity
Predicate location P40 FINISHED
Object Enfield Lock E596133 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: Enfield Lock | Statement: [RSAF Enfield, location, Enfield Lock]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Enfield Lock
Context triple: [RSAF Enfield, location, Enfield Lock]
  • A. Enfield Lock chosen
    Enfield Lock is a suburban district in north London known for its historic Royal Small Arms Factory site and proximity to the River Lee Navigation.
  • B. Rosedale Lock
    Rosedale Lock is a navigational lock on Ontario’s Trent–Severn Waterway that helps boats transition between different water levels along the canal system.
  • C. Allington Lock
    Allington Lock is a key navigation and flood-control lock on the River Medway in Kent, England, marking the tidal limit of the river.
  • D. Camden Lock
    Camden Lock is a historic canal lock and bustling market area in Camden Town, London, known for its alternative culture, shops, and street food.
  • E. Hampstead Lane Lock
    Hampstead Lane Lock is a navigation lock on the River Medway in Kent, England, used to manage water levels and enable boat passage along the river.
  • 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_69ca82bcb4848190a9a9d036ad768642 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb43b7dbd881908a80f23090596eae completed March 31, 2026, 3:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc9482113881909439c9e43fbc933f completed April 1, 2026, 3:44 a.m.
Created at: March 30, 2026, 5:34 p.m.