Triple

T6948060
Position Surface form Disambiguated ID Type / Status
Subject Battle of Brentford E160849 entity
Predicate location P40 FINISHED
Object Brentford E91229 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: Brentford | Statement: [Battle of Brentford, location, Brentford]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brentford
Context triple: [Battle of Brentford, location, Brentford]
  • A. Brentford chosen
    Brentford is a suburban town in West London, England, situated at the confluence of the River Brent and the River Thames.
  • B. Brentford F.C.
    Brentford F.C. is a professional English football club based in West London that competes in the Premier League.
  • C. Watford
    Watford is a large town in Hertfordshire, England, known for its proximity to London, major shopping and entertainment facilities, and its professional football club, Watford FC.
  • D. Fulham
    Fulham is a district in southwest London, England, known for its riverside location along the Thames, residential character, and historic football culture.
  • E. Brentford and Isleworth
    Brentford and Isleworth is a UK parliamentary constituency in west London that includes the towns of Brentford, Isleworth, and surrounding areas along the River Thames.
  • 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_69c68850419081909fb426b8f5a304c7 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6daabc624819091a03289241b43c8 completed March 27, 2026, 7:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69c75870719481908312b387a3c6ce81 completed March 28, 2026, 4:26 a.m.
Created at: March 27, 2026, 2:28 p.m.