Triple

T10037374
Position Surface form Disambiguated ID Type / Status
Subject MX Brougham E205204 entity
Predicate nameContains P5298 FINISHED
Object Brougham E692827 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: Brougham | Statement: [MX Brougham, nameContains, Brougham]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brougham
Context triple: [MX Brougham, nameContains, Brougham]
  • A. Brougham
    Brougham is a small historic community and neighbourhood within the City of Pickering in Ontario, Canada.
  • B. Brougham chosen
    Brougham is a small village and civil parish in Cumbria, England, known for its historic castle and proximity to the town of Penrith.
  • C. Royal Brougham
    Royal Brougham was a prominent Seattle sportswriter and editor known for his long career at the Seattle Post-Intelligencer and his significant influence on the city's sports culture.
  • D. Lagonda
    Lagonda is a historic British luxury car marque renowned for its high-performance grand tourers and association with Aston Martin.
  • E. Arrol
    Arrol is a Scottish surname most notably associated with Sir William Arrol, a prominent 19th-century civil engineer known for major bridge-building projects.
  • 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_69ca834f70e88190b2d74828b7767ec1 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cdcede428c8190ae115dc3425f9b0e completed April 2, 2026, 2:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69d282608d688190832c37442f53099a completed April 5, 2026, 3:40 p.m.
Created at: March 30, 2026, 8:55 p.m.