Triple

T6623174
Position Surface form Disambiguated ID Type / Status
Subject London Borough of Ealing E149725 entity
Predicate hasTwinTown P919 FINISHED
Object Bielany E416525 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: Bielany | Statement: [London Borough of Ealing, hasTwinTown, Bielany]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bielany
Context triple: [London Borough of Ealing, hasTwinTown, Bielany]
  • A. Bielany chosen
    Bielany is a northern district of Warsaw, Poland, known for its residential neighborhoods, green spaces, and connection to the city center via the Warsaw Metro.
  • B. Brzesko
    Brzesko is a town in southern Poland known for its historical architecture and regional brewing traditions.
  • C. Parczew
    Parczew is a small town in eastern Poland known for its historical roots and location within the Lublin region.
  • D. Wołosate
    Wołosate is a small village in southeastern Poland’s Bieszczady Mountains, known as a remote hiking base and the terminus of the Main Beskid Trail.
  • E. Bartoszyce
    Bartoszyce is a town in northern Poland known for its historical architecture and location near the border with Russia’s Kaliningrad Oblast.
  • 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_69c687ed8a9c81908bb671717cb192ef completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6af7decb08190a7b1ddb95e534a6a completed March 27, 2026, 4:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69d4d14df7888190aadd3f506b6b4cd2 completed April 7, 2026, 9:41 a.m.
Created at: March 27, 2026, 1:58 p.m.