Triple

T5521021
Position Surface form Disambiguated ID Type / Status
Subject A473 road E144806 entity
Predicate connects P390 FINISHED
Object Talbot Green E538715 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: Talbot Green | Statement: [A473 road, connects, Talbot Green]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Talbot Green
Context triple: [A473 road, connects, Talbot Green]
  • A. Talbot Green chosen
    Talbot Green is a retail and commercial village in Rhondda Cynon Taf, South Wales, known for its shopping centre and role as a local economic hub.
  • B. Brook Green
    Brook Green is a public park and residential area in the Hammersmith district of West London, known for its tree-lined green space and surrounding Victorian and Edwardian housing.
  • C. Englefield Green
    Englefield Green is a village in Surrey, England, known for its proximity to Runnymede and its large common land.
  • D. Richmond Green
    Richmond Green is a historic open space and recreational common in Richmond, London, known for its picturesque setting, cricket matches, and surrounding period architecture.
  • E. Langley Green
    Langley Green is a residential neighbourhood within the town of Crawley in West Sussex, England.
  • 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_69c008f873a481909b4d9f7e2db3c37d completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01f7227a8819080c9f074afe0eaac completed March 22, 2026, 4:57 p.m.
NED1 Entity disambiguation (via context triple) batch_69c059d3494c8190b20e57ec4d73d3fa completed March 22, 2026, 9:06 p.m.
Created at: March 22, 2026, 3:33 p.m.