Triple

T7800422
Position Surface form Disambiguated ID Type / Status
Subject Putney E180415 entity
Predicate hasLandmark P105 FINISHED
Object Putney Bridge E222841 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: Putney Bridge | Statement: [Putney, hasLandmark, Putney Bridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Putney Bridge
Context triple: [Putney, hasLandmark, Putney Bridge]
  • A. Putney Bridge chosen
    Putney Bridge is a historic road and foot bridge over the River Thames in London, linking Putney on the south bank with Fulham on the north.
  • B. Queen’s Bridge
    Queen’s Bridge is a notable road bridge spanning the River Tay in Perth, Scotland, serving as a key crossing point into the city.
  • C. Queen’s Bridge
    Queen’s Bridge is a historic road bridge in Belfast, Northern Ireland, carrying traffic across the River Lagan near the city centre.
  • D. Queen’s Bridge
    Queen’s Bridge is a historic bridge in Bound Brook, New Jersey, known for carrying traffic across the Raritan River and serving as a key local crossing point.
  • E. Lambeth Bridge
    Lambeth Bridge is a road and foot traffic bridge over the River Thames in central London, linking Lambeth and Westminster near several major political and religious landmarks.
  • 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_69ca827e50cc8190a92a733577184938 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cae98765c48190b325eee67bd663fc completed March 30, 2026, 9:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69cbdec158788190aae5038ea72f2a99 completed March 31, 2026, 2:48 p.m.
Created at: March 30, 2026, 4:33 p.m.