Triple

T26258667
Position Surface form Disambiguated ID Type / Status
Subject Basel region E656784 entity
Predicate hasCrossBorderAgglomeration P128764 FINISHED
Object Trinational Eurodistrict Basel 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: Trinational Eurodistrict Basel | Statement: [Basel region, hasCrossBorderAgglomeration, Trinational Eurodistrict Basel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCrossBorderAgglomeration
Context triple: [Basel region, hasCrossBorderAgglomeration, Trinational Eurodistrict Basel]
  • A. hasCrossBorderArea chosen
    Indicates that an entity is associated with or spans a geographic area that extends across national or jurisdictional borders.
  • B. hasCrossBorderCenter
    Indicates that an entity operates or is associated with a center whose activities, services, or scope extend across national borders.
  • C. haveCrossBorderCorridor
    Indicates that there exists a designated corridor or route enabling movement or interaction across a national or regional border between the related entities.
  • D. hasCrossBorderTies
    Indicates that there exists a relationship or connection that extends across national or jurisdictional boundaries between the involved entities.
  • E. hasCrossBorderCommuting
    Indicates that there is a regular pattern of commuting across national borders between the related entities.
  • F. None of above.

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_69ee5b4d25ac819086acb51184602576 completed April 26, 2026, 6:37 p.m.
NER Named-entity recognition batch_69f65aa07c048190a5df30d53d8f0cf5 completed May 2, 2026, 8:12 p.m.
PD Predicate disambiguation batch_69f659cc571c819097e51e531961d812 completed May 2, 2026, 8:08 p.m.
Created at: April 26, 2026, 9:09 p.m.