Triple

T3857254
Position Surface form Disambiguated ID Type / Status
Subject Anderlecht E90047 entity
Predicate hasNeighbour P5707 FINISHED
Object Uccle E138086 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: Uccle | Statement: [Anderlecht, hasNeighbour, Uccle]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Uccle
Context triple: [Anderlecht, hasNeighbour, Uccle]
  • A. Uccle chosen
    Uccle is a leafy, affluent municipality in the Brussels-Capital Region of Belgium, known for its residential character and diplomatic presence.
  • B. Oxted
    Oxted is a commuter town in southeast England known for its proximity to London and location at the foot of the North Downs.
  • C. Esher
    Esher is a suburban town in the borough of Elmbridge in Surrey, England, known for its affluent residential character and proximity to London.
  • D. Uxbridge
    Uxbridge is a township in Ontario, Canada, known for its rural landscapes, trail networks, and proximity to protected natural areas.
  • E. Uxbridge
    Uxbridge is a suburban town in West London, England, known as a major commercial and administrative centre and the terminus of a branch of the London Underground.
  • 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_69aed95b3c088190a8f85d19e6070599 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeec09312c81908ffd7441c83730c8 completed March 9, 2026, 3:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69b5041f40f88190883339db0950026a completed March 14, 2026, 6:45 a.m.
Created at: March 9, 2026, 3:19 p.m.