Triple

T20037401
Position Surface form Disambiguated ID Type / Status
Subject Swisshelm Park E497311 entity
Predicate near P350 FINISHED
Object Regent Square NE NERFINISHED

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: Regent Square | Statement: [Swisshelm Park, near, Regent Square]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Regent Square
Context triple: [Swisshelm Park, near, Regent Square]
  • A. Regent Square chosen
    Regent Square is a leafy, historic Pittsburgh neighborhood known for its walkable streets, classic homes, and proximity to Frick Park.
  • B. Lismore Square
    Lismore Square is a local shopping centre serving the retail and service needs of the community in Lismore, Ireland.
  • C. Georgetown Square
    Georgetown Square is the historic downtown district of Georgetown, Texas, known for its preserved Victorian-era architecture, local shops, restaurants, and community events.
  • D. Havelock Square
    Havelock Square is an area in Singapore known for housing key legal institutions, including the Family Justice Courts.
  • E. Waverley Square
    Waverley Square is a commercial and transit-oriented neighborhood in Belmont, Massachusetts, known for its local shops and MBTA commuter rail station.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69da627278c88190babe4297a9df1236 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e662e935ac8190900cdb4f0cfde505 completed April 20, 2026, 5:31 p.m.
Created at: April 11, 2026, 3:36 p.m.