Triple

T13323129
Position Surface form Disambiguated ID Type / Status
Subject Bruton Place E317363 entity
Predicate locatedIn P40 FINISHED
Object Mayfair E922340 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: Mayfair | Statement: [Bruton Place, locatedIn, Mayfair]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mayfair
Context triple: [Bruton Place, locatedIn, Mayfair]
  • A. Mayfair
    Mayfair is a residential neighborhood located within the city of Homewood, Alabama.
  • B. Mayfair chosen
    Mayfair is an affluent central London district known for its luxury shops, exclusive residences, and prestigious hotels and restaurants.
  • C. Knightsbridge
    Knightsbridge is an affluent central London district renowned for its luxury shopping, upscale residences, and proximity to Hyde Park.
  • D. Mayfair neighborhood
    The Mayfair neighborhood is a predominantly residential area in Northeast Philadelphia known for its rowhomes, strong community identity, and commercial corridor along Frankford Avenue.
  • E. Belgravia
    Belgravia is an affluent, predominantly residential district in central London known for its grand terraces, garden squares, and embassies.
  • 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_69d806b4d62c81908d4ced1665414be5 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69d9992ab83c8190982d9f54dff6919f completed April 11, 2026, 12:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69f71f2cd5688190a2a0db0f0295de83 completed May 3, 2026, 10:10 a.m.
Created at: April 9, 2026, 9:30 p.m.