Triple

T23131756
Position Surface form Disambiguated ID Type / Status
Subject A234 road E577186 entity
Predicate connects P390 FINISHED
Object Sydenham E236913 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: Sydenham | Statement: [A234 road, connects, Sydenham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sydenham
Context triple: [A234 road, connects, Sydenham]
  • A. Sydenham
    Sydenham is a district in east Belfast, Northern Ireland, known for its residential areas and proximity to key transport links including George Best Belfast City Airport.
  • B. Sydenham
    Sydenham is an inner-city suburb of Christchurch, New Zealand, known for its mix of residential areas, light industry, and retail precincts.
  • C. Sydenham chosen
    Sydenham is a suburban district in southeast London, England, known for its Victorian architecture, green spaces, and residential character.
  • D. Sydenham
    Sydenham is the former name of the Canadian city now known as Owen Sound in Ontario.
  • E. Somervile
    Somervile is an alternative spelling of Somerville, a name commonly associated with various towns, institutions, and surnames of English and Scottish origin.
  • 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_69e245f7b0e481909c473ff4e6a54e2c completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18e88909881908c695cd7d39d380c completed April 29, 2026, 4:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0c30872b5c81909433a0e3c9e3af00 completed May 19, 2026, 9:42 a.m.
Created at: April 17, 2026, 4 p.m.